CKEditor significantly slower when SCAYT is enabled

[Erik Kangas]

Many customers and ourselves have noticed that CKEditor has a much slower response to keyboard input when SCAYT is enabled. The speed seems to be vary over an editing session.

Anecdotally, it seems to be worse if you are far geographically from the SCAYT server.

We would expect SCAYT to be as unobtrusive as possible. I.e. perhaps not doing anything until the user has paused in editing for at least a second or so, and not blocking on any AJAX calls.

This uses CKE 3.1.1 and the latest SCAYT back-end release from last week.

[Erik Kangas]

This is a much more serious issue than previously thought. We are having many complaints from many different users using many different machines. We have seen the issue in the latest versions of Chome and Firefox (and it probably affects other browsers).

As you type in a SCAYT-enabled CKEditor, the speed of the keyboard response starts to slow down after a few paragraphs, getting very sluggish. The more content you type, the worse it gets until for some users, the browser starts to lock up. If you start with more content in the editor, the issue happens faster.

We are talking a new KB of text to see this issue, not very much.

I have to tell anyone complaining to disable SCAYT.

I would classify this as a pretty critical issue, especially with SCAYT enabled by default now.

[Frederico Caldeira Knabben]

We'll be investigating this issue. Thanks for the details.

For now, you may eventually disable the automatic SCAYT startup with the ​scayt_autoStartup setting.