Re: [w3c/uievents] Should an element remain focused and receive key events if it's display:none-ed? (#236)

I agree that the blur behavior in this case is not important for site compatibility, and we can change the HTML specification. However, dispatching no events and keeping `activeElement` aren't logical and such behavior would be a pitfall for web developers. So I wonder if we can define an algorithm which is easily implementable.

A wild idea is to add something like activeElement-focsusable-check step to [Update the rendering](https://html.spec.whatwg.org/multipage/webappapis.html#update-the-rendering).  It can handle many cases such as disconnecting focused element, changing tabindex/contenteditable attributes, changing disabled state as well as loosing CSS box.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents/issues/236#issuecomment-507622880