id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
4688	SCAYT affecting IsDirty and ResetIsDirty.	irpf		"Using 2.6.5. Windows NT.  FireFox 3.0.15.

There seems to be some kind of timing/race condition that causes ResetIsDirty to fail (or causes something else to come along later, after ResetIsDirty has been called, and flags the editor as ""dirty"") if
1) SCAYT is enabled and 
2) there is at least one misspelled word somewhere within the editor text (highlighted with a red underline).

The specific scenario involves retrieving the editor contents (HTML) from a database and setting it into the editor via SetText. Obviously, I don't want this newly retrieved text to be considered ""changed/dirty"" (from the user's perspective) so within the OnAfterSetHTML handler I invoke ResetIsDirty. This works perfectly and reliably...UNLESS the conditions mentioned above are present. In the SCAYT scenario, the invocation of ResetIsDirty that occurs within OnAfterSetHTML seems to be ignored or something else comes along after it's invoked and marks the editor as dirty, perhaps as a result of the slight delay introduced by the spell check operation that eventually marks the incorrect word with the red underline. The end result is that the editor says it is Dirty even though no editing of the text has occurred.

Thank you."	Bug	closed	Normal	CKEditor 3.3	UI : Spell Checker	FCKeditor 2.6.5	fixed	Confirmed, HasPatch	WebSpellChecker.net