Define all focus events #3514
Labels
integration
Better coordination across standards needed
interop
Implementations are not interoperable with each other
topic: focus
Comments
annevk
added
interop
|
As of 2 years ago, DOMFocusIn & DOMFocusOut were only in Blink and WebKit. |
|
If these get added to the spec, is it safe to assume they will be added to the GlobalEventHandlers mixin? (That makes it easier for SVG, to just defer standardization to HTML.) |
|
DOMFocusIn/DOMFocusOut usage stats for Chrome: |
This was referenced Mar 21, 2022
Closed
This was referenced Aug 24, 2022
josepharhar
added a commit
to josepharhar/html
that referenced
this issue
Mar 29, 2024
These events are already implemented in browsers and are documented on MDN. This PR also adds onfocusin and onfocusout event handler content attributes. whatwg#3514 tracks this and other focus events. Fixes whatwg#10234
|
I created a PR to define focusin and focusout: #10235 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should at least define
and maybe
if they are still implemented in most browsers.
uievents/order-of-events/focus-events/has some tests.w3c/uievents#88 has a discussion by @dtapuska @smaug---- et al about changing existing implementations to be more useful. It seems that needs to be resolved one way or another before we take action here.
I also somewhat feel it'd be more logical for HTML to define all the bits related to focus events, such as
FocusEvent, since it already defines the dispatching logic. It doesn't make much sense to me for that to be defined in https://w3c.github.io/uievents/#events-focusevent and results in fragmented discussion about how these events ought to work.(This supersedes https://www.w3.org/Bugs/Public/show_bug.cgi?id=25897.)
The text was updated successfully, but these errors were encountered: