-
-
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
Do not remove focused element from the DOM #5493
Comments
I wanted to do it now but there are some tricky cases like where to put the focus before removing |
Couldn't |
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). |
In some browsers (Firefox, Edge, Safari) the active (focused) element does not fire blur event when is removed from the DOM. It might cause some issues related to the
FocusTracker
https://github.com/ckeditor/ckeditor5-link/issues/193 or even more freaky issues like autocomplete attached to the void #1501. I'm sure we have similar issues with the image balloons.It should be a good practice to move the focus from the element before removing it. However, it is easy to forget about it and it is not easy to track the related bugs. We decided to log a warning when a focused element has been removed from the DOM.
The text was updated successfully, but these errors were encountered: