Fix Firefox 20.0 "transitionend" handler #742

Closed
wants to merge 1 commit into
from

Projects

None yet

3 participants

@swain

when there is no effcient detector for event support, monitor standard with compatible event type.

#741 fixed

@mislav
Collaborator

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?

@swain

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.

@swain swain closed this Apr 17, 2013
@mislav
Collaborator

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.

@mislav mislav reopened this Apr 17, 2013
@mislav
Collaborator

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?

@miketaylr

FWIW, mozTransitionEnd has never been implemented in Firefox. The lowercase (per spec) transitionend is required.

@mislav mislav was assigned Nov 24, 2013
@mislav mislav changed the title from fix issue #741 to Fix Firefox 20.0 "transitionend" handler Jul 7, 2014
@mislav
Collaborator

Sorry I've been slow on this. Is this still an issue?

@mislav mislav added the Needs confirm label Jul 7, 2014
@mislav
Collaborator

Closing as this seems like a non-issue. Firefox 20+ works well for me.

@mislav mislav closed this Jul 7, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment