Open putzwasser opened 3 years ago
This unfortunately is not possible yet due to how input detection works. But there's a high chance it will be resolved soon once we migrate to beforeInput.
This unfortunately is not possible yet due to how input detection works. But there's a high chance it will be resolved soon once we migrate to beforeInput.
Thanks for the reply. Is there an ETA for the migration?
Also, do you know a workaround?
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.
This is still relevant
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.
This is still relevant
📝 Provide detailed reproduction steps (if any)
[Ctrl]+[Shift]+u
to switch into unicode input mode✔️ Expected result
CKeditor should insert a non-breaking space
❌ Actual result
CKeditor inserts a normal space.
❓ Possible solution
Respect the actual user input. While I understand that ckeditor tries to deliver a good experience when copy pasting (#1669), I find it quite bold to replace deliberately chosen user input.
(This is related to #1669 but this describes another bug. While #1669 deals with copy-pasting a nbsp this is about inserting it directly via unicode input mode)
If you'd like to see this fixed sooner, add a 👍 reaction to this post.