1. Open api.html sample in IE9-10
2. Enable SCAYT
3. Insert below text in textarea <span style="color:red">red</span>
4. Select 'om' from "This is s[om]e ..."
5. Press insertHTML button to insert span
   Result: In IE9-10 span with red color is removed.

1. Please see ticket: http://dev.ckeditor.com/ticket/11084
2. Please use 11084.html sample - just put it into samples folder of editor
3. Open page
4. Click inside editor and type few words
5. Click Kill editor
6. Click Rebuild editor
7. Click inside editor
   Result: No focus. Cursor can't be put inside content are with click. This doesn't happen when scayt_autoStartup is set to false.

Problem can be reproduced in IE9-10 only.

Reproducible with the latest (major) CKEditor and SCAYT. I was testing it on Chrome.

1. Open image2 sample.
2. Enable SCAYT.
3. Go to nested editable and type some incorrect word.
4. Try to correct it using options in context menu.
5. Word is corrected, but caret is moved back to the main editable.

As I mentioned in #16 it's important on Blink/Webkit to focus the correct editable element. The editor takes care of that (in editable.focus()), so I guess that SCAYT is not using this method.

1. Open image2 sample.
2. Enable SCAYT.
3. Focus nested editable (image caption).
4. SCAYT button is switched to off although SCAYT still works.

The same happens when moving focus from nested editable to main editable.

With CKEditor 4.3 release we're introducing Widget System. There is an issue where SCAYT does not perform spellchecking within nested editables.

Sample TC:

1. Open image2 sample.
2. Make some mistakes in nested editable.
3. Enable SCAYT. Mistaken words within nested editable are not underlined.

see http://dev.ckeditor.com/ticket/10878

1. Open api.html sample in Blink, Webkit or Firefox
2. Enable SCAYT
3. Insert below text in textarea
   <span style="color:red">red</span>
4. Select 'om' from "This is s[om]e ..."
5. Press insertHTML button to insert span
6. Word gets underlined
7. Select misspelled word, right-click on it and change it to one of suggested words.
   Result: both spans (red and misspelled) are removed but in editor elements path there is still span present and if you click on it JS error is thrown.

This may look like editor issue but IMO SCAYT should not remove red span. This is source of the error.

I tested this on IE11 and IE9:

1. Open replacebycode sample.
2. Enable SCAYT.
3. Type something in few paragraphs, so undo steps are recorded.
4. Scroll the viewport so not entire editable is visible.
5. Undo - viewport will be scrolled. Additionally, I think that editor is blurred for a moment.

Tested and confirmed in CKEditor 4.4.0 prerelease
Browser: Latest Chrome

1. Open this sample https://gist.github.com/adelura/4745832744f039c80b68
2. Put caret in Apollo ^11
3. Enable SCAYT
   • Actual Result: header split in two

Sample TC:

1. Open in Firefox http://nightly.ckeditor.com/full/samples/replacebycode.html
2. Wait 5 seconds for the editor to load fully
3. Enable SCAYT, wait 5 seconds
4. Click Source button, wait few seconds

In Firebug error console., the following error is shown:

TypeError: _3cf(...) is null

loader__base.js (line 3586)

Now click Source button again:

TypeError: doc is null

loader__base.js (line 2844)

CKEditor does not go back to Wysiwyg mode.

Tested and confirmed in CKEditor 4.4.0 prerelease
Browser: IE11

1. Open this sample https://gist.github.com/adelura/6b5395a27fe199be4044
2. Focus editor and enable SCAYT (editor is blurred - bug reported in #42)
3. Focus editor again and wait.
   • Actual Result: word is no highlighted, but should be because is incorrect

Steps:

1. Open plugins/image2/samples/image2.html
2. Enable SCAYT and click Image
3. View CKEditor's elements path

Expected result: < body > < image >

Actual result: < body > < div >

1. Open readonly sample.
2. SCAYT button is disabled.
3. Switch to source and back to wysiwyg.
4. SCAYT button is enabled.

Or instead of switching between modes, make editor readonly and editable again.

Tested and confirmed in CKEditor 4.4.0 prerelease
Browser: IE9

1. Open this sample https://gist.github.com/adelura/0888d6d2d7282e1a9aa9
2. Wait until evething is loaded
3. Click on editor
   • Actual Result: editor disappear

Our page use custom value for document.domain and there is following code in the https://svc.webspellchecker.net/scayt26/_base.xd.js:

var html="javascript:void(0)";

var _69b=_4.doc.createElement("iframe");

_4.attr(_69b,{hidefocus:"true",frameborder:"0",src:html});

_4.body().appendChild(_69b);

_69b.contentWindow.document.open();

_69b.contentWindow.document.write("<html><head></head><body><script type="text/javascript">scayt=parent.scayt;scayt.iframeOnLoad()</script></body></html>");

_69b.contentWindow.document.close();

(I removed some lines that actually doesn't case this bug).

So, it creates blank iframe (with src = javascript:void(0)). And after that calls iframe.contentWindow.document methods. But there is a known issue in the IE that iframe with blank src won't work if document.domain is set in the parent page (see workarounds here: http://stackoverflow.com/questions/14715427/cant-access-an-aboutblank-iframe-in-ie-after-the-document-domain-changes). Access to iframe.contentWindow.document crashes with "access is denied" message.

Are there any way to receive js from webspellchecker with support for custom document.domain?

Tab containing informations about SCAYT in dialog is disabled. Therefore clicking About option in editors, will display options tab.

TC:

1. open editor
2. click SCAYT button
3. click About SCAYT option

Scenario:

1. Open browser (tested with FF and Chrome).
2. Open samples/replacebyclass.html.
3. Enable SCAYT.
4. Wait for it (wait till "Aldrin" is underlined).
5. Press Cltr+A, Cltr+X to remove content.

You will see error in console:
Uncaught TypeError: Cannot read property 'parentNode' of undefined.

It is important to remove content after SCAYT starts ("Aldrin" is underlined) but before it finished.

Hi,

During testing phase for CKEditor 4.3 beta which introduced Widgets System we found this issue: http://dev.ckeditor.com/ticket/10876.

Widgets are non-editable elements which can have nested contenteditable elements inside them. These nested editables have to be really carefully handled. One of the problematic things is focusing them, because they are separate focusable element beside the main editable.

When reproducing a TC described in #10875 I found these lines from SCAYT plugin:

}else{
if((/CKEDITOR/i.test(this.assocApp))&&evt.ctrlKey&&evt.charCode==118){
setTimeout(function(){
t.containerNode.focus();
},0);
}else{
t.containerNode.focus();
}

This code is executed on keydown and it moves focus from nested editable to containerNode which is the main editable (body element).

I don't understand why SCAYT does such a thing, but if it really needs to it should call focus on the editor.editable() which will assure that focus is moved to the nested editable, not to the main one. Although, I think that the best solution would be to get rid of these focus() calls at all, because it's really hard to predict their result.

Tested and confirmed in CKEditor version: 4.3.3 and 4.4.0 (prerelease)
Browsers: all

1. Load the following content in editor

   <p>wrongspell</p>
   

   • Expected Result: The word is red-marked in wyswig mode.

2. Set cursor after 'g' letter

   <p>wrong^spell</p>
   

3. Press 'enter' at the cursor position

   • Expected Result: The marker underline is removed immediately after key down
   • Actual Result: The marker will remain for a while until next refresh happens.

Original bug reported at: http://dev.ckeditor.com/ticket/5701

1. Clone ckeditor-dev repo.
2. Clone SCAYT inside plugins dir.
3. Add SCAYT to extraPlugins.
4. Open inlineall sample.

Error is thrown:

[11:53:59.145] TypeError: this._.removeFormat is undefined @ http://localhost/cksource/ckeditor-dev/plugins/removeformat/plugin.js:142

SCAYT incorrectly tests for removeFormat. It may be loaded, but not initialized yet, since SCAYT doesn't require remofeFormat. So better test is needed than:

editor.addRemoveFormatFilter && editor.addRemoveFormatFilter( scaytFilter );

1. Clone ckeditor-dev repo.
2. Clone SCAYT inside plugins dir.
3. Add SCAYT to extraPlugins.
4. Type "Quisque"
5. Make RMB click on "Quisque"

Expected result: SCAYT context menu is shown
Actual result: SCAYT context menu is not shown

Hi,
I have an issue with CKEditor 4.3.2 (free) with the SCAYT plugin (free).
We don't like the double line spacing caused by P tags and have changed the setting config.enterMode = CKEDITOR.ENTER_BR; in the config.js file.
The trouble is that this causes the spell checker to move the cursor as you type.
For instance:
If I have a blank CKEditor, enter a character (say Q) and then move the cursor to the left of this character.
If I press enter it moves the cursor to AFTER the character.
If I then move the cursor up to the top of the page, it moves itself back down.
If I then turn the spell checker off this stops happening.
Is the config.enterMode = CKEDITOR.ENTER_BR; no longer supported?
Is there another way of stopping the double line spacing?
Or is this an issue with the spell checker?
Thanks
Michael

Tested and confirmed in CKEditor 4.3.3 and 4.4.0 (prerelease)
Browsers: Mainly in Chrome

1. Copy to clipboard following text:
   sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdfsdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdfsdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf sdf
2. Enable SCAYT
3. Paste above text quickly for a few(depends on system performance) times into editable area
4. Press Enter and type some misspelled word
   • Actual Result: Browser freezes for some period of time

Tested and confirmed in CKEditor 4.3.3 and 4.4.0 (prerelease)

Browsers: IE8 & IE9

1. Load editor with configuration
   enterMode: CKEDITOR.ENTER_BR
2. Load editor with no content
3. Create two element list with misspelled words
4. Escape list with double enter
5. Type some misspelled word below list
6. Enable SCAYT
   • Actual result: list is split into two parts.

Browsers: All

1. Load editor with configuration
   enterMode: CKEDITOR.ENTER_BR
2. Set content:
   `
   1. kldsjfkslj
   2. sdklfjskld
   sdjklfj ` or `

   Apollo 11

   Apollo is okay `
3. Enable SCAYT
   • Actual result: list(first content) or header(second content) is split into two parts.

Bug may be related to: http://dev.ckeditor.com/ticket/8929

Tested and confirmed in CKEditor 4.3.3 and 4.4.0 (prerelease)
Browsers: all

1. Load the following content in editor

   <p><a name="anchor1">anchor mis</a>pell</p>
   

2. Wait until word "mispell" is marked by SCAYT

   • Actual Result: marker splits up the anchor into two, with each of them get applies the anchor styles.

3. Click "source button" to get into source mode

4. Click "source button" to get into editor mode

   • Actual Result: creates new anchors

Original bug reported at: http://dev.ckeditor.com/ticket/7812

1. open Chrome,
2. open "Mathematical Formulas" sample (samples/plugins/mathjax/mathjax.html),
3. enable SCAYT,
4. double click on any formula to open dialog.

Wield delay will appears. Sometimes it lasts couple seconds.

We have an issue where the red underline on some words is showing as a red box that is large and causing a problem with display.

Using ATD plugin for ckeditor.

Reported on: http://dev.ckeditor.com/ticket/10394

1. Open ckeditor.com/demo
2. Enable SCAYT
3. Open SCAYT language tab

Actual results: broken elements on tab
Expected results: markup should be correct

1. Enable SCAYT
2. Paste some text in Latin (Lorem ipsum dolor sit amet enim. Etiam ullamcorper. Suspendisse a pellentesque dui, non felis. Maecenas malesuada elit lectus felis, malesuada ultricies.) and wait until words became underlined
3. Right-click one of misspellings (Lorem) to be sure that there is "No suggestion" option
4. Type some misspelling (testt) and wait until it became underlined
5. Right-click the misspelling to be sure that there are some suggestions
6. Right click one of Latin misspellings (Lorem)

Expected result: there are "Ignore", "Ignore All", "Add Word", "No suggestion" and default CKEditor menu items
Actual result: there are suggestions for the misspelling which was clicked before (testt) and "Ignore", "Ignore All", "Add Word", "No suggestion" and default CKEditor menu items

Hi,

Enable SCAYT and try to select text from the bottom upwards. See the screencast - ​http://www.screencast.com/t/SsQJEch3T2

When SCAYT finishes checking selection works as expected. SCAYT uses bookmarks and selection on checking and it resets the editor selection.

Ticket in CKEditor - http://dev.ckeditor.com/ticket/11157
IMHO this isn't anything critical. Can this even be fixed on your side or the way checks are made can't be changed?

Steps:

1. Open sample page with SCAYT 3 + CKEditor 4
2. Try to open the context menu for a misspelled word to display the banner
3. Try to click the links

Expected result: Links are clickable

Actual result: Links are not clickable

Steps:

1. Open sample page with SCAYT 3 + CKEditor 4 and Inline mode
2. Open SCAYT Options dialog
3. Click OK
4. View console

Expected result: SCAYT Options dialog is closed without errors

Actual result: SCAYT Options dialog is closed with error:
Uncaught IndexSizeError: Index or size was negative, or greater than the allowed value. ckeditor.js:371

When config.readOnly mode is passed in inline configuration, SCAYT button is enabled, although it should not be enabled.

CKEDITOR.replace( 'editor1', {
    readOnly : true,
} );

Note that to reproduce the issue, you shoud not use the readonly sample distributed with CKEditor, because the button is disabled when editor.setReadOnly() is called there http://ckeditor.com/latest/samples/readonly.html

Hi,

We've just found that SCAYT cannot be enabled on CKEditor 4.2. It tries to override CKEDITOR.plugins.undo.Image#equals which does not exist any more. It was split into two methods - equalsContent and equalsSelection. I guess that you'll be interested in the first one, although it's not a good practice to override private methods. Therefore maybe listening on new editor#change event will be a better option. Note that it will be introduced in CKEditor 4.2 too.

Steps:

• Get the https://github.com/ckeditor/ckeditor-presets
• Switch to major branch.
• Update submodules (git co submodule update)
• Build (./build.sh full all --leave-js-unminified)
• Open any sample.
• Try to enable SCAYT.

Reported here:http://dev.ckeditor.com/ticket/11462

1. Enable SCAYT
2. Create the new paragraph and set "Formatted" format
3. Type "test" and move cursor to the start of the text ("|test")
4. Hit shift+enter twice

Expected: the two new lines are added above the text. cursor stays at the start of the text.

Outcome: the second hitting shift+enter will create the new line under the text and move the cursor into it.

1. Open CKEditor with SCAYT. Let's say http://ckeditor.com/demo#full
2. Run SCAYT.
3. Select different language so many words get underlined (i.e. French).
4. R-click underlined word -> Ignore
5. R-click another underlined word -> Add word
6. Repeat 4-5. In most of the cases, the browser's tab hangs (100% CPU core load) for the second or third word.
7. Even if nothing freezes, an excessive usage of CPU can be observed which implies the overall slow-down of the browser.

Reproduced in latest Chrome. Other browsers possibly affected.

Reported here http://dev.ckeditor.com/ticket/11036.

Steps to reproduce:

1. Open www.ckeditor.com/demo in IE
2. Enable SCAYT
3. Write 3-4 paragraphs
4. Try to undo the text

Undo does not work properly and unable to undo all text inserted (undo just blocks).
Problem can be reproduced in IE8-10 from CKEditor 3.6.2.
Please also have a look at attached screen cast to that ticket.

Could you leave a comment if this is editor or scayt issue?

Steps to reproduced:
1. Set: CKEDITOR.config.scayt_autoStartup = false;
2. Open sample page with SCAYT 3 + CK 4 in IE 9
3. Open SCAYT menu in Inline mode
4. Click 'Enable SCAYT'

Expected result:
SCAYT should be enabled, misspelled words should be underlined

Actual result:
Toolbar is hidden after SCAYT launching in inline mode

Tested and confirmed in CKEditor 4.4.0 prerelease
Browser: Latest Chrome

1. Open this sample https://gist.github.com/adelura/8c440212f84875c1e3b5
2. Enable SCAYT
3. Next to 'Apollo 11' text type some two misspelled words for example
   fooor baaar
4. Wait until words get underlined
5. Use 'Check Spelling' option from SCAYT/WSC plugin menu button
6. Click 'Finish Checking' and wait until words get underlined
7. Select word 'fooor'

8a. Press Ctrl + C

• Actual Result: selection is gone and selected word doesn't get copied to clipboard

8b. Press Backspace

• Actual Result: Word is not deleted as expected. Cursor move left, and only space is deleted

Tested and confirmed in CKEditor 4.4.0 prerelease
Browser: IE9

1. Open this sample https://gist.github.com/adelura/4745832744f039c80b68
2. Scroll content area down
3. Type some misspelled words at the end of second blockquote
4. Enable SCAYT, wait for words to get underlined
5. Right-click on misspelled word
   • Actual Result: content area will jump up for a split of a second.

I have CKEditor v4.1.0 installed along with SCAYT. Everything works fine except that in IE10, SCAYT does not auto start (it works fine if you disable and reenable). I have the following in my config.js file:

config.scayt_autoStartup = true;

Auto startup works fine in all the other browsers. Any ideas?

1. Open http://ckeditor.com/demo#full
2. Enable SCAYT (it's 005c91b).
3. Right-click several words to fix spelling.
4. Press CTRL-Z to undo each change. Note that a single CTRL-Z reverts the substitution.

Now use the latest SCAYT and repeat all the steps. Note that each substitution requires two CTRL-Z to be undone: the first one that moves the caret and the second one that reverts the word.

Hi, the scayt plugin it checks for opera and air and disables itself if running that, I could not find the reason why in the comments or the code. I removed those checks and what I noticed is calls for window.scayt but this property is never asiogned any value in the plugin.js. I would apreciate if someone could let me know why is not working on Adobe AIR maybe I can workaround that. Here is a forum thread I started abgout this. P.S. version 4 of ckeditor is not working in AIR so I can't try that.

Steps:

1. Open sample page with SCAYT 3 + CKEditor 4 in inline mode
2. Open Languages dialog
3. Change Language > Close the dialog
4. Unfocus the editor
5. Open Languages dialog again

Expected result: Languages dialog is opened without errors

Actual result: JS error.
Object doesn't support this property or method options.js?t=E2I8, line 3 character 397

Details and file are attached here: http://dev.ckeditor.com/ticket/11245

To reproduce:
Load attached file (there are enter_BR and empty editor contents)
Enable scayt
Type two misspelled words separated with Enter
Wait until there is red underline and right-click on words.

Steps:

1. Open Image 2 sample page
2. Next to Apollo 11 header paste: ‘adamr udarek schol wolek’
3. Enable SCAYT
4. Open WSC pop-up
5. Click Finish Checking and wait for the words to get underlined again.
6. Select Word ‘udarek’ and press Ctrl+C

Expected result: The word is copied

Actual result: Selection is gone and selected word doesn’t get copied to clipboard.

I initially reported it in http://dev.ckeditor.com/ticket/10888 but that's not the right issue tracker :-) so here it goes:

When I try the sample of CKEditor 4.3 Beta with the language plugin enabled, enter there content in a different language:

<span dir="ltr" lang="es">
El invierno pasado estuvo tan fr&iacute;o que literalmente se form&oacute; hielo en mi barba.&nbsp;
</span>

and then start SCAYT, it will underline the whole text, even though it has the proper Spanish dictionary included. It happens because it treats the whole content as if it was written in English.

JSDuck builder report:

Warning: ~/ckeditor-docs/repos/ckeditor-plugin-scayt/plugin.js:765: Unsupported tag: @example

1. Clone ckeditor-dev repo.
2. Clone SCAYT inside plugins dir.
3. Add SCAYT to extraPlugins.
4. Fix issue #2.
5. Open inlineall sample.

• Expected: No SCAYT button.
• Actual: There's SCAYT button in toolbar and it can be enabled. But nothing more than that works.

1. Open IE9.
2. Open CKEditor 4.2.2 (or 4.2.1).
3. Go to "inlinebycode.html" sample.
4. Enable SCAYT.

Page will jump down. It looks like SCAYT srolls the page every time it find new unknown word.

https://docs.google.com/file/d/0B3ZPryvDDIOPSW1zbGlmNmlUbUk/edit?usp=sharing

Reproducible with the latest (major) CKEditor and SCAYT. I was testing it on IE9.

1. Open image2 sample.
2. Enable SCAYT.
3. Place caret in nested editable.
4. Try to disable SCAYT.
5. Error is thrown. Unfortunately IE says that the error is thrown from HTML file, so I haven't got more details regarding it.