ckeditor
[Firefox] Caret is missing when inline image is at the end of line
📝 Provide detailed reproduction steps (if any)
- Add inline image to empty paragraph or at the end of the line
- Click right after it
- Try to type something
✔️ Expected result
The caret is visible, you can type.
❌ Actual result
The caret is not visible, you cannot type. You need to select the image, click arrow right and then type something.
Screencast
https://user-images.githubusercontent.com/34380544/134302736-7e4496c8-c875-4599-ac91-3c555dc3bf02.mp4
📃 Other details
- Browser: …
- OS: …
- First affected CKEditor version: …
- Installed CKEditor plugins: …
If you'd like to see this fixed sooner, add a 👍 reaction to this post.
This is actually quite an awkward issue because we’re supporting custom smileys based on images. These can naturally occur at the end of a line and block the placement of the caret after the smiley. We do suppress the image toolbar for those smileys so at the end all that happens is that the image is being added to the text selection and nothing else.
The workaround with the arrow key is hardly a substitute to resolve this problem: Not only are common users (rightfully) not aware of this and this isn’t even an option on entirely touch based devices. For these users it is currently impossible to set the caret after the image without deleting the image!
@niegowski by any chance the recent work in the empty inline elements could somehow solve also this problem?
@niegowski by any chance the recent work in the empty inline elements could somehow solve also this problem?
No, it's not related. But this could be related: https://github.com/ckeditor/ckeditor5/issues/12267
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.
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).
@Witoso It looks like your bot is malfunctioning, it shouldn’t have closed this issue?
Clarification: The bot checks new reactions to the ticket. We'll think about considering also reactions to the bot's comments – this would make sense.
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.
Tested with the latest demo running v46.0.1, this is still a huge problem for Firefox users.