[IE]: SCAYT affecting IsDirty

[Jakub Ś]

This is the continuation of #4688

WebSpellChecker team has been reported CheckDirty functionality doesn't work correctly after replacing misspellings with correct word. While preparing solution we discovered additional problem in IE. Here are steps to reproduce:

1. Open ​http://ckeditor.com/demo in any IE
2. Enable SCAYT and wait for all misspellings would be underlined
3. Change editor's mode to <Source> then to <WYSIWYG>
4. Run in console CKEDITOR.instances.editor1.checkDirty()

NOTE: For the above steps you can use api sample

Expected result: checkDirty=false
Actual result: checkDirty=true

Problem has been reproducible in all versions of IE from CKEditor 3.0

[Frederico Caldeira Knabben]

Unfortunately this patch is not acceptable. It may make the checkDirty function very unstable. For example, if somehow we change the checkDirty function logic, it'll not work well when SCAYT is enabled.

It is clear that the problem is the getSnapshot call, which needs to get fixed by SCAYT on the checkDirty call. Because of this, the logic could be somehow similar, but made in a way that the getSnapshot result is fixed. Something like this (untested... just the relevant "if" part inside the override function):

var oriGetSnapshot = editor.getSnapshot;
editor.getSnapshot = function()
{
	return scayt_instance.reset( oriGetSnapshot.apply( this, arguments ) );
}
retval = org.apply( this, arguments );
editor.getSnapshot = oriGetSnapshot;

In this way we don't touch any original functionality of the editor, avoiding any possibility of breaking it.

[WebSpellChecker.net]

Here is another patch which address the comments