-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Minor Glitch: CKEditor "placeholder" clashes with LinkCommand #9776
Comments
Hi, thanks for the report. I tried this on the docs page and also locally but I was unable to reproduce this fully. Placeholder text indeed does not disappear, but the selection is always at the beginning of a paragraph: 0_placeholder1.mp4Maybe apart from link plugin, you use some custom plugins or some specific plugins combination causes this? |
@FilipTokarski, thanks for your response. I can confirm: For the docs page it works as well for me (within Chrome). I tried to strip down the plugins and ended up with:
And the effect is the same, i.e. cursor is at the end of the placeholder text. Thus, either there is some other side-effect or it is the version (we are at 24.0.0, cannot easily check for up-to-date version). Another observed difference: If we focus our editor, the placeholder disappears. If I focus the editor in CKEditor documentation, the placeholder text remains until you start typing. |
Thanks for the details. It's exactly as you described, this new behaviour was introduced in version P.S.
You can use:
|
📝 Provide detailed reproduction steps (if any)
placeholder
in your CKEditor configuration. See Editor placeholder - CKEditor 5 Documentation.✔️ Expected result
Just as for other inline styles (e.g. Bold), the text area is cleared and the link-popup appears.
❌ Actual result
The placeholder text is not removed, the cursor placed at the end of the placeholder text and the link-popup appears:
Fortunately, if you set a link and submit
LinkCommand
form view, the placeholder text is gone and the link is written to the text area as expected.📃 Other details
If you'd like to see this fixed sooner, add a 👍 reaction to this post.
The text was updated successfully, but these errors were encountered: