when there is no effcient detector for event support, monitor standard with compatible event type.
when there is no effcient detector for event support, monitor standar…
…d with compatible event type.
Interesting approach. I'd rather listen to only 1 event type, however. Is there no way to detect whether a Firefox version requires or doesn't require the "Moz" prefix?
I find an blog article here Detecting event support without browser sniffing written in 2009. This approach I think is also not efficient & graceful enough.
However, my approach isn't graceful either. But up to now, no one browser supports 2 events with "standard" & "compatible" simultaneously. so I don't worry about one browser will tigger the event handler twice.
I'll reopen this to think about your solution some more. It isn't a bad solution. I also don't think there's chance that the transitionend event might get triggered twice.
I've just taken a look and I can't figure out what's broken with Firefox 20. It works the same as Firefox 19. We've never listened to "MozTransitionEnd", but just "transitionend" for Firefox. What is #741 all about?
FWIW, mozTransitionEnd has never been implemented in Firefox. The lowercase (per spec) transitionend is required.
Sorry I've been slow on this. Is this still an issue?
Closing as this seems like a non-issue. Firefox 20+ works well for me.