Spec onanimation* event handlers, and ontransitionend (and webkit versions)

[miketaylr]

See https://bugzilla.mozilla.org/show_bug.cgi?id=911987

[foolip]

document.createEvent("WebKitTransitionEvent") has surprisingly high usage in Chrome, perhaps it's used in feature detection.

@annevk @cdumez

[annevk]

Feel free to PR DOM if removing it is too much trouble. I have a hard time caring.

[foolip]

I haven't done any research on why usage is high. There's always a risk that things like this actually lead you into a WebKit-only branch which would create risk for Gecko, so it'd be good to take a look first. Of course, if any Edge och Gecko engineer said they want to spec and implement it right now, I'd be 100% on board.

[karlcow]

It could be testing indeed.
https://github.com/trevorlinton/webkit.js/search?utf8=%E2%9C%93&q=document.createEvent%28%22WebKitTransitionEvent%22%29

Things like: webkit.js and angular mock

• https://github.com/search?q=document.createEvent%28%22WebKitTransitionEvent%22%29&type=Code&utf8=%E2%9C%93
• https://github.com/angular/bower-angular-mocks/blob/9b42d4ab7a260e1ad11ab50e9f1f1eb3db039d58/angular-mocks.js

[karlcow]

Related to #118 ?

[stephenmcgruer]

It is not clear to me what this bug covers at this point.

• The onanimation* and ontransition* event handlers are nowadays spec'd in css-animations-1 and css-transitions-1
• Mention was made of document.createEvent("WebKitTransitionEvent"): Chromium dropped both WebKitTransitionEvent and WebKitAnimationEvent in the last few years: 1, 2, 3, 4

It seems this should be closed in favour of #118 , but does anyone know a reason to keep this open and separate?