-
Notifications
You must be signed in to change notification settings - Fork 2.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
Make focus events composed #3511
Comments
This sounds reasonable to me. |
This sounds reasonable, however, I think there are several checkpoints before changing the behavior:
ping also @rniwa. |
@hayatoito implementations already have this behavior. See the tests I wrote (linked from the PR). |
Ah, I see. Please forget my previous comment. I thought I forgot to make it composed. I had updated UI events spec at w3c/uievents#91. |
No, the UI Events specification doesn't really define these events or when they get dispatched. HTML defines that at https://html.spec.whatwg.org/#fire-a-focus-event. I filed w3c/uievents#185 to simply stop defining these in UI Events to make this less confusing. |
I got it. Thank you for the explanation. |
Tests: web-platform-tests/wpt#9683. Fixes #3511.
Tests: web-platform-tests/wpt#9683. Fixes whatwg#3511.
Since focus events are UI events, they should be composed. https://html.spec.whatwg.org/multipage/interaction.html#fire-a-focus-event needs to be updated and I guess we should add some tests.
(Note that #1583 captures other issues around focus.)
cc @whatwg/components
The text was updated successfully, but these errors were encountered: