(In reply to Markus Stange [:mstange] from comment #0) > In Firefox, a SMIL animation end event will notify both "end" and "endEvent" listeners: [...] > Can we switch to Chrome's behavior and only notify `endEvent` listeners? > > The two other types with the same problem are `beginEvent` and `repeatEvent`. Yeah, it looks to me like this should be fine. I'm not finding any spec support for `begin`, `end`, or `repeat` as event names. I suspect we support them by accident as a result of the fact that the `onfoo` attributes for these events have no `Event` suffix. (See e.g. https://www.w3.org/TR/SVG2/interact.html which pairs up `beginEvent` with `onbegin`, etc. At some point in the past, I'll bet the only [or most-straightforward] way to support `onbegin` was to support `begin` as an event name, and that wart stuck around.)
Bug 1845381 Comment 9 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Markus Stange [:mstange] from comment #0) > In Firefox, a SMIL animation end event will notify both "end" and "endEvent" listeners: [...] > Can we switch to Chrome's behavior and only notify `endEvent` listeners? > > The two other types with the same problem are `beginEvent` and `repeatEvent`. Yeah, it looks to me like this should be fine. I'm not finding any spec support for `begin`, `end`, or `repeat` as event names. I suspect we support them by accident as a result of the fact that the `on***` attributes for these events have no `Event` suffix. (See e.g. https://www.w3.org/TR/SVG2/interact.html which pairs up `beginEvent` with `onbegin`, etc. At some point in the past, I'll bet the only [or most-straightforward] way to support `onbegin` was to support `begin` as an event name, and that wart stuck around.)