SCAYT's loader stucks under the file:// protocol

[Sa'ar Zac Elias]

After the autoload configuration became enabled by default in [5500], FF throws this error:

uncaught exception: Could not load cross-domain resources: scayt._base scayt.nls.caption

The culpritis is line 856 in ​SCAYT's loader script.
In IE, SCAYT stucks the browser for a while, and after that, an 'Uncaught Exception' error is displayed.

[WebSpellChecker.net]

Checked out trunk again and could not reproduce the problem. May be there are some additional conditions?

[Sa'ar Zac Elias]

I'm using the replacebycode sample, IE8 and FF 3.6.3.
You probably didn't wait long enough. At the first time it took long before IE got stuck but after that it happend almost instantly. In ff, it might take a minute but eventually the error will be thrown.

[Sa'ar Zac Elias]

Firebug shows that SCAYT includes these scripts:

<script type="text/javascript" src="file://svc.spellchecker.net/spellcheck31/lf/scayt24/_base.xd.js"></script>
<script type="text/javascript" src="file://svc.spellchecker.net/spellcheck31/lf/scayt24/nls/caption.xd.js"></script>

The protocol of these scripts is file://, so the file is not available. That might be the reason why the throw statement is used at the first place.

[Frederico Caldeira Knabben]

Ok, confirmed. It works on a web server, but it's not working under the ​file:// protocol. It's enough to open an editor sample directly from the file system.

[Garry Yao]

It's a matter of SCAYT's dojo loader timeout, not of priority now.

[WebSpellChecker.net]

What behavior is expected:

• SCAYT disables SCAYT button if protocol is not http[s]
• if protocol is not http[s] SCAYT still tries to load (using http protocol) and suppress expected error messages

[Frederico Caldeira Knabben]

For the 3.3, we must not have any error being thrown at least. Ideally, SCAYT must still work by loading from ​http://.

[WebSpellChecker.net]

fixed on spellchecker.net side.

the behavior is: if protocol is not http[s] SCAYT still tries to load (using http protocol) and suppresses expected error messages

[Garry Yao]

We still have the described issue in IE.

[WebSpellChecker.net]

There were different symptoms in IE (it freezes - but later, after timeout, start working), caused by banner ad code. Now this problem fixed on spellchecker.net side.

Is there any additional info on steps to reproduce?

[Garry Yao]

It works fine now.