Second chance to find respectively type of event handler

[dSalieri]

2. If event’s type attribute value is a match for any of the strings in the first column in the following table, set event’s type attribute value to the string in the second column on the same row as the matching string, and return otherwise.

Event type	Legacy event type
"animationend"	"webkitAnimationEnd"
"animationiteration"	"webkitAnimationIteration"
"animationstart"	"webkitAnimationStart"
"transitionend"	"webkitTransitionEnd"

I saw this table not once, but I really can't understand why is there only 4 names of event handlers?

Why don't we see for example "transitionstart" or "transitioncancel" and so on?

Need clarification about this movement in direction these names.

[annevk]

Did you look in blame for context? Did you write a test for the other names you expect?

[dSalieri]

@annevk Idk where I can look blame of this table. I checked out webkitTransitionStart, webkitTransitionCancel and I didn't find anything. So I can conclude we have only 4 props because we had no others valid in past time.

[annevk]

https://github.com/whatwg/dom/blame/main/dom.bs (or in your local checkout).

[dSalieri]

@annevk oh thanks, I really tried to find how to watch blame. I've read everything what related with it. And my opinion haven't changed: in the past existed these 4 events with webkit prefix and now events with webkit additionaly supported for compatibility.

[bathos]

@dSalieri I’m not 100% sure I get what you’re asking, but there are only four because those were the only four needed to address the motivating compat issue. Ideally, there would be none.