SCAYT plug-in update

[WebSpellChecker.net]

We have updated SCAYT core and SCAYT plug-in

Some problems were resolved:

#3768 SCAYT setting must not use an object tree #3562 Reload SCAYT before insertElement

There is still open issue in IE with the "new document" and actually we assume with the setData method processing by SCAYT. On "new document" and for example when we try to use WSC (it finish its' work with call to setData) we getting "Permission Denied" error in SCAYT when SCAYT tries to access editable document innerHTML property. At the same time when editor is constructed from the scratch or "source" command is used SCAYT works (i.e. able to access to editable document) without errors.

If you have any thoughts/suggestions on editor behavior on setData vs creating new editable control could you please let us know.

[WebSpellChecker.net]

patch proposed

[Garry Yao]

The patch make SCAYT working much better with editor modifications, but there's an obvious issue with IE:

Reproducing Procedures

1. Open the replace by class example page in IE;
2. Click on 'SCAYT' -> 'Enable SCAYT';
   • Actual Result: The toolbar button state shows SCAYT is enabled, despite the fact that SCAYT is not enalbed on the document.
3. Click on 'SCAYT' -> 'Enable SCAYT' again;
   • Actual Result: Now SCAYT is enabled

Regard the 'new page' integration issue:

There is still open issue in IE with the "new document"...

Could you illustrate the codes you used to work with 'setData' please? And I wonder why it's not reside in plugin.js to have it under open discussion.

[WebSpellChecker.net]

We're in progress reviewing the problem with IE.

SCAYT core does not use setData - it interacts directly with editable iframe element, but the problem can be easily reproduced in IE if

1. type some text with misspellings

2. enable SCAYT

3. start WSC

4. update misspellings in WSC

5. click Finish Checking in WSC: at this point setData is called by WSC. After setData performed (we can see that because content of editor is changed) there are JS errors - one of them is permission denied - same as (or similar to) the problem which happens when "new document" button is clicked.

In the SCAYT plug-in we are using contentDom event to create or re-create SCAYT instance. This even was introduced to us by CK team during adaptation of SCAYT plug-in code to the CKeditor - may be processing of this event is the reason for the problem. We are in progress with this also and would like to get any suggestions if there are any.

[WebSpellChecker.net]

The problem with enabling SCAYT in IE on second click is inside SCAYT core. We're going to updated it and update this ticket when the problem will be fixed.

[Garry Yao]

Come with a new patch comply more with our codebase, I would ask you SpellChecker.net please check it to get this committed.
I'll open new ticket for the specific IE bug.

[WebSpellChecker.net]

patch looks ok.

one note on the code which set default parameters values:

CKEDITOR.config.scayt_maxSuggestions = CKEDITOR.config.scayt_maxSuggestions CKEDITOR.config.scayt_autoStartup = CKEDITOR.config.scayt_autoStartup

5;

false;

In your code parameters are hard-coded and not checking whether they are already set. Does the config.js processed after plug-ins are loaded?

[Frederico Caldeira Knabben]

Replying to SpellChecker.net:

In your code parameters are hard-coded and not checking whether they are already set. Does the config.js processed after plug-ins are loaded?

Yes, that's the correct way to set the configuration options, and the custom settings from config.js will properly override them.

[Garry Yao]

Fixed with [3857].