Safari: SCAYT + offline causes floatpanel and dialog issues

[Tobiasz Cudnik]

SCAYT + offline causes floatpanel and dialog issues.

Reproduce

1. Go offline (or steal SCAYT hostname in OS's hosts file).
2. Use multi-instance example (eg Skins) from local machine.
3. Don't disable SCAYT.
4. Start opening floatpanels (may be only color ones) in various instances.
5. Try to open dialogs in same way.

Result

1. Some of floatpanels don't appear at all.
2. Dialogs almost always appears with big delay.

Expected

1. Everything functions same as when SCAYT host/webservice works.

I think this is very important thing to consider when we decide to ship CKEditor with SCAYT enabled by default. Editor installations shouldn't be affected by (possible) SCAYT downtimes. Other browsers may also be affected.

[WebSpellChecker.net]

We cannot reproduce this. Please provide more clear steps to reproduce.

[Garry Yao]

It can reproduce with a slow connection to SCAYT server in Firefox with ​Throttle plugin,

actually a common problem in all browsers, where SCAYT scripts loading is blocking the executing (though loaded in parallel) of other laterly requested editor resources.

[Frederico Caldeira Knabben]

You need to setup svc.spellchecker.net in your hosts file to point to an invalid IP. In this way, the SCAYT scripts will not get loaded by the browser.

The problem here is quite serious, as any other script execution in the page is blocked while SCAYT scripts are not loaded and executed. This can be an issue with slow connections also, which can impact effectively on the load of editor files, when opening the styles combo, or any dialog, for example.

There may be a solution for that, but we need to understand if it really works. At runtime, SCAYT should create an <iframe>, compatible with the current page, and load all scripts into that iframe. I think that, in that case, the script loading time will not block the execution of other scripts in the page.

This impact all browsers.