ckeditor
Deleting characters in Android Chrome leaves cursor in wrong position
While troubleshooting a separate issue, I found that I have trouble with deleting characters I've just typed in Chrome on my Android phone.
Because the original issue was discovered in Firefox on my phone, these steps were repeated in each browser, but the issues remained distinct with each browser exhibiting it's own bug.
📝 Provide detailed reproduction steps (if any)
- Visit the Classic editor at https://ckeditor.com/ckeditor-5/demo/editor-types/
- Type a few words, like "Delete this" (pause a second to avoid default behavior of deleting previous whole word with one press of the backspace)
- hit backspace a first time
- The last character is deleted, but the cursor is left at the wrong position: "Delete th|i" (pipe inserted to show resulting position)
- hit backspace a second time: "Delete t|h"
- hit backspace a third time "Delete t|" (oddly, this is the one time the cursor is left in the CORRECT position)
- hit backspace a fourth time (once only, space character between words is jumped): "Delete| "
- hit backspace a fifth time: "Delet|e"
- etc...
✔️ Expected result
When backspace is hit, delete only the first adjacent character to the left, leaving the cursor after all remaining text, including spaces.
❌ Actual result
Typing a few characters and then hitting the backspace just as many times (common behavior when you realize your last thee key strikes were errors, for example) results in deleting unintended character(s), leaving at least one of the known mistakes.
📃 Other details
native keyboard Android 14 Samsung Galaxy S22 Ultra One UI version 6.1 Firefox 128.0.3 Chrome 127.0.6533.65
If you'd like to see this fixed sooner, add a 👍 reaction to this post.
Most likely a duplicate of some issue in our typing improvements (#16289), which will have a fix released in the next release. Please confirm it's gone by using the nightly docs.
The issue lacks the feedback we asked for two weeks. Hence, 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.
We've closed your issue due to inactivity. We understand that the issue may still be relevant. If so, feel free to open a new one (and link this issue to it).