Open karlshea opened 11 years ago
Thanks for this. This seems trivial to do, if anyone is willing to contribute a working patch I'd be happy to merge it in.
Actually, hmm. This may not be trivial to do... Transit needs to support both the WebkitTransition
/webkitTransitionEnd
and WebkitTransition
/transitionEnd
combinations.
The way Transit works now is that it assumes the same prefix for the transitionEnd
event as what prefix is used in the transition style. Transition end events need to be handled differently now.
I think the event names that Chrome supports must have changed. My callback isn't getting called since it's trying to attach to transitionEnd instead of webkitTransitionEnd.
When I change the value of 'transition' to 'webkitTransitionEnd' in the eventNames object everything works just fine.