According to this bug:
http://dev.ckeditor.com/ticket/5853
There is a known performance issue with the SCAYT feature of CKEditor. However this bug is over 3 years old and has not been updated for that long.
Is there any plan to improve the performance of SCAYT or do we just have to accept it needs to be disabled.
Thanks!
Ben
SCAYT has been modified
SCAYT has been modified countless times since then so there's a pretty good chance this isn't valid anymore. If you're using an older version of CKEditor I suggest you try out the latest version of CKEditor: http://ckeditor.com/download
Customer and Community Manager, CKSource
Follow us on: Facebook, Twitter, LinkedIn
If you think you found a bug in CKEditor, read this!
We did recently update the
We did recently update the version - so I don't think that is the answer.
I see similar problems on the latest demo page if SCAYT is enabled, particularly using IE or Chrome.
http://ckeditor.com/demo
If it's fixed, or modified, it would be useful if the bug report was updated - otherwise how can we know.
To solve this we have disabled SCAYT and enabled the native spell checker in the browser. It's a shame because the SCAYT feature was useful for IE users but was causing too many problems.
I let one of the devs see the
I let one of the devs see the ticket. He'll have a look.
Customer and Community Manager, CKSource
Follow us on: Facebook, Twitter, LinkedIn
If you think you found a bug in CKEditor, read this!
A big issue
Along with this, when we have the config.scayt_autoStartup = true in our config.js file, our users cannot select large text from bottom to top or RTL. Because of this type of delay is also involving the mouse select functionality. It happens in the most current version as well if the scayt is set to automatically starting up.