Hi Dan,

I have got some update for you on the F11 issue with IE. There is a work in progress now to standardize the layout mechanism across all browser types. What this means is that the HTML DOCTYPE will change to a standard one and there should be no "manual" layouting needed for IE any more, the process that hangs IE under certain conditions.

Although I don't have it fully confirmed yet, then my understanding is that this should be included in the next release, which I take for the next stabilization release that we will publish. Whether that means it will be included in both WinWeb and .NETHTML5/JQT I do not know yet.

And no, I don't have a date for that release yet.

Palli

 Hi Mitch,

The reason for this is well known as being the recursive layouting triggered in IE when you resize the browser, most notablly when you go to full screen using F11 for instance. I take it that you do not get this problem for other browsers, right ?

In any case, the new DOCTYPE, html, introduced in the .NETHTML5 version (our future framework, combining XSLT and JQT into the same core) will not have this problem. For testers, I took .NETHTML5 and tested F11 in both IE8 and IE9 and it works fine without any apparant hickups.

Hope this helps,

Palli

 Hi Mitch,

I hope you don't really mean CFEditor, and instead you really mean CKEditor. In that case, there should be no problem for you going for .NETHTML5, as I updated CKEditor for .NETHTML5 support the day after I got the first report on it's incompatibility with that version. I have not seen any reports to confirm or complain on that fix, so I assumed it would be working fine.

Please let me know if CKEditor needs further adaption to .NETHTML5.

Palli