Prefixing event handlers (a-la onWebkitAnimationEnd)
See original GitHub issueThe following works great for browsers that don’t need a prefix, but fails for browsers that do.
<div onAnimationEnd={this.onAnimationEnd} />
What is the best way to handle this for browsers that need the webkit
prefix for this event?
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Prefixing event handlers (a-la onWebkitAnimationEnd) #1263
I played with this a little bit tonight, but not seeing any of the prefix extensions fire. Tried all of the following variations....
Read more >Element: animationend event - Web APIs | MDN
The animationend event is fired when a CSS Animation has completed. ... The same, but using the onanimationend event handler property:.
Read more >How to handle vendor prefixing for event handlers in Scala.js?
The simplest solution is to polyfill the API with its spec'ed name, redirecting to the vendor-prefixed versions. For example, in a ...
Read more >XML Events - W3C
Abstract. The XML Events module defined in this specification provides XML languages with the ability to uniformly integrate event listeners ...
Read more >206170 – onwebkit{animation, transition}XX handlers missing ...
The event handlers are: * onwebkitanimationend * onwebkitanimationiteration ... And does this affect only the prefixed handlers?
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
You could use a simple helper function to add prefixes:
Thanks a ton @developit . This is working well.
My final solution looks something like this: