Unable to select text (for a moment) after enabling SCAYT

[jswiderski]

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?

[KremYura]

Hi,

This is known issues in SCAYT. And there are more then one related issues in CKEditor Ticket system. (e.g http://dev.ckeditor.com/ticket/8485).

This bug can be reproduced only when user uses backward selection. And no problem with forward selection.

With new bookmark implementation (will be released by the end of December) we can detect forward and backward selection, but restoring of backward selection still isn't implemented.

We will keep you posted about the changes in this functionality.

[jswiderski]

Hi,

Thanks for finding a duplicate:)

[paoloumali]

Hi,

Do you have a fix or patch? This may seem minor but for end users, they think that the editor is problematic.

[brett415]

I agree. This is a problem. Our customers have emailed us asking what is wrong with the editor. Once customer even sent a video showing their cursor automatically moving to the right. Once they turned off SCAYT it stopped.

I don't understand how this would be considered a minor issue? When it is turned on you cannot select text properly. That is a major issue.

[KremYura]

We don't consider this as a minor issue, however the solutions isnt't available yet.
We have a task in our Bug Tracking System to implement this except IE which lacks the ability to programmatically set the direction of a selection.
We plant back to the issue when we done with other critical issues like: #65, #69, #71

[WebSpellChecker]

The issue is fixed in SCAYT CORE and will be available after release 4.6.1 scheduled at the end of November 2014.

[WebSpellChecker]

We'd like to inform that the fix has been released in version 4.6.1 and already available for hosted users.