-
-
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
The panel jumps after clicking on an item when the marker is a link. #4661
Comments
@jodator is the above gif another test case for the same issue or is it a different thing? TC:
|
@mlewand is there a mention instance or only I'm for similar but different: here there's a race between Link UI and Mention UI and one of them should always win - I'm not sure which one as this is selection change not typing. With typing the Mention UI is obsious winner. |
It's plain text only. So same race here. |
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. |
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). |
Found by @Mgsy.

My 2¢:
Kinda is - internally the marker to which UI panel is positioned is removed so as described I have to return position to something - here this is selection - better would be to skip such positions (https://github.com/ckeditor/ckeditor5-ui/issues/503). I can see that after a while the panel is positioned to link anyway.
Other possible fix is to change the marker management logic entirely. Do not ever remove the mention marker - only update it if need (but I'm not sure if such logic will be easy enough to implement as currently logic checks if marker exists on some occasions...
The text was updated successfully, but these errors were encountered: