Hi,
We've been waiting for years to get this "Resizing of tables, columns and rows" feature in the editor, which you finally implemented it in release 2016.3.914, thank you very much.
However, the selecting and resizing of the entire table in the IE-11 browser is extremely very difficult.
1. It's required user to really do a lots of mouse pointer narrowing in order to select the table and then start resizing it.
2. Many of the times when selecting the table and move the mouse in order to select the table marker for resizing, the table get unselected automatically by mouse move! It's very buggy.
3. In Dot Net WebBrowser object the "Editor Add Table" shortcut which highlight the number of rows and columns to add table, is not working unless add via Table Wizard. Please test and fix this bug in .Net WebBrowser object (System.Windows.Forms.WebBrowser).
Thank you.
3 Answers, 1 is accepted
Thank you for your valuable feedback!
For 1 we already have a logged bug report.
For 2, I logged a new one which you can access here.
For 3, I'm afraid that we cannot help since the Windows.Forms.WebBrowser renders the content in IE7 compat mode, which is not among the supported browsers by Kendo.
We do appreciate your bug reports and I've updated your Telerik points for them.
Best regards,
Rumen
Telerik by Progress
Rank 1
Hi Rumen,
Thank you for your kind reply. Noted your reply on Problem # 1 and 2 and looking forward to hear from you when the bug fixes will be released?
As for Problem #3, your reply is not actually true. The .Net Windows.Forms.WebBrowser will honour and renders the content in the latest installed IE browser version, if user add the following meta tag inside the HTML page head:
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
By Adding the above meta tag, we currently can perfectly render all Kendo UI components in Windows.Forms.WebBrowser. The only exception we encounter is what I mentioned in Problem #3 which I believe it's bug in the Kendo not the WebBrowser object.
Please kindly look into this issue and help to fix the problem.
Thank you.
Can you please verify with acid test that rendering engine used by the WebBrowserControl is indeed Edge by loading this page: www.chisono.it as suggested in this blog http://www.codewrecks.com/blog/index.php/2011/06/06/witch-version-of-browser-is-used-by-the-webbrowser-control/.
If the UserAgent string corresponds to Edge and you still get the same unwanted result (which unfortunately we cannot control in the Windows WebBrowser control), you can try the last possible approach to incorporate WebKit into your app: http://sourceforge.net/projects/webkitdotnet/.
Best regards,
Rumen
Telerik by Progress