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

> 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.

That's probably the only sane way to define this behavior.

-- 
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-509515664