This problem manifests only in IE - it seems like IE9 is worse than IE8. Sadly, 80%+ of our user-base is IE (corporate standard in most places, and alomost all of our clients have locked down PCs so they can't just download and use FF).
I think this issue is almost a show-stopper for us going onto the winweb version. We have actually encouraged our customers to use F11 to get more screen space. So earlier today, the first thing my main client did while testing was to push F11 - and then crashed her browser - not a good start.
The problem is that if we switch to the NETHTML5 build we lose support for CFEditor. Is there any timeline on getting that wrapper working on the HTML5 build?
I feel like i am caught between two bad options: have CFeditor support and risk crashing the browser, or having a safe broweser and no CFEditor support.
Your advice is welcome!