IF1.8 trunk revision 44808/ IE11, Tomcat 6.0.35 /component-showcase [faceletes-enh] > Rich Text demo:
1) When clicking the "Source" icon, the source code is rendered in the component, however this causes the IE11 browser to crash.
User is unable to click any other icon on the demo, and a browser message is displayed at the bottom of the page: "localhost is not responding"; if clicking the "Recover webpage" button, the page is reloaded.
2) The "Permission denied" console error was still reproduced in IE11/ IE7, when switching toolbar mode between "Basic" and "Default", and also switching tabs between "Rich Text", "Description" and "Source" :
IE7:
Line: 12
Error: Permission denied.
IE11:
SCRIPT70: Permission denied
File: ckeditor.js, Line: 780, Column: 58
3) Compared to IE7/8, Firefox, Chrome, in IE11 there is no separate "Spell Check As You Type" icon rendered in the component, besides the "Check Spelling" icon.
Is this an issue?
4) Spell Checker JS errors:
a) In IE11 in Spell Checker, after enabling SCAYT, clicking on any of "Options, "Languages", "Dictionaries", "About SCAYT" triggers a JS error:
SCRIPT5022: SyntaxError
File: ckeditor.js, Line: 107, Column: 85
b) In IE7/8, a JS error occurs when using Spell Checker > Spell checking options.
Steps:
- type a text in the component.
- click "Check Spelling" icon -> Spell Check window opens up.
- click "Options" button on "Spell Check" window.
- on "Spell checking options" select a few options, then click "Ok" -> JS error:
IE7:
Line: 27
Error: 'JSON' is undefined.
IE8:
Message: No such interface supported
Line: 28
Char: 3
Code: 0
URI: http://s1.webspellchecker.net/spellcheck3/lf/opt_b.js?7193
r45077: committed fixes for error popups when using the spellchecking plug-in.
Indeed, those errors are very random, and it's not always possible to reproduce them. I noticed that these errors were more likely to happen when quickly clicking different buttons and menu options, without giving a good pause for all the operations to complete before clicking something else. They also seemed more likely to happen after clearing the browser's cache.
These commits try to fix those errors that we know about. There might still be other random error messages, but they don't affect the normal functioning of the editor. It could also be that these errors are seen on our test machines because they are slower. I couldn't reproduce these errors using IE11 in previous versions modes.
As for the last issue, the error occurs in the third-party website code, and we don't have any control over it.