-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Demix animation events from GlobalEventHandlers #16531
Demix animation events from GlobalEventHandlers #16531
Conversation
This pull request has merge conflicts that must be resolved before it can be merged. |
This pull request has merge conflicts that must be resolved before it can be merged. |
This pull request has merge conflicts that must be resolved before it can be merged. |
1 similar comment
This pull request has merge conflicts that must be resolved before it can be merged. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Like with most bubbling events we have too many entries. I've read https://drafts.csswg.org/css-animations/#events and Chromium's implementation, and it looks like the event target is always an Element
for these events. Can you move the 4 entries to Element
and remove everything else?
This pull request has merge conflicts that must be resolved before it can be merged. |
This pull request has merge conflicts that must be resolved before it can be merged. |
This pull request has merge conflicts that must be resolved before it can be merged. |
This PR demixes the
animation
event handlers from the GlobalEventHandlers mixin. There were some odd discrepancies between the events already on the interfaces. Here's what I found:The
animation
events were set to43
, however the event handlers said they were added in43
only onWindow
then79
everywhere else. After some further research, it appears that the events were added in43
, and then the event handlers were added later other than for Window.Additionally, the
Window
event had prefixes added to them, which came from #3563. However, this appears to have been a mistake; the same PR added the features forDocument
andHTMLElement
which don't have the prefix data, and the description indicates intention to remove it. I've removed it here.