IndexSizeError iPad Japanese characters

[mark-bragg]

Is this a bug report or feature request? (choose one)

🐞 Bug report

💻 Version of CKEditor

CKEditor5 classic 1.0.0-beta.3

📋 Steps to reproduce

1. Build ckeditor into an ipad app
2. use hardware keyboard with Japanese Romaji as the input
3. open the app and type characters into editor
4. delete some characters
5. type another character (notice the completion suggestion box moves to the upper left corner of html view)--this is where an IndexSizeError is thrown from within ckeditor.js

Additional Steps that result in a cascade type problem:
6. delete another character--error is thrown again (let X be the current visible text)
7. reselect the editor and type any number of characters appended to original string
8. within JS, if at this point you call getData() on the editor, only X will be returned.

✅ Expected result

completion suggestion box stays underneath position of typed text within the editor

❎ Actual result

completion suggestion box moves to the upper left corner of html view

📃 Other details that might be useful

When debugging the app, I noticed there was an IndexSizeError thrown from within ckeditor.js

[Reinmar]

Most likely one of many IME issues.

@Mgsy do you confirm it?

[Mgsy]

I'm able to reproduce it. I've received the same error:

[Error] IndexSizeError: The index is not in the allowed range.
    getRangeAt (article.js:20699)
    domSelectionToView (article.js:20699)
    _handleSelectionChange (article.js:44700)
    (anonymous function) (article.js:44662)
    fire (article.js:2276)
    domListener (article.js:15681)

Tested on iOS 11.3.

[CKEditorBot]

There has been no activity on this issue for the past year. We've marked it as stale and will close it in 30 days. We understand it may be relevant, so if you're interested in the solution, leave a comment or reaction under this issue.

[CKEditorBot]

There has been no activity on this issue for the past year. We've marked it as stale and will close it in 30 days. We understand it may still be relevant, so if you're interested in the solution, leave a comment or reaction under this issue.

[CKEditorBot]

We've closed your issue due to inactivity over the last year. We understand that the issue may still be relevant. If so, feel free to open a new one (and link this issue to it).