Closed Bug 713844 Opened 13 years ago Closed 13 years ago

transitionEnd event doesn't fire if CSS properties did not change during the transition

Categories

(Core :: General, defect)

9 Branch
x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: andrej.okonetschnikow, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.63 Safari/535.7 Steps to reproduce: Apply transition with duration >= 0 to an element but do not update any of CSS properties during the transition. Test case http://jsfiddle.net/NpdcJ/1/ Actual results: transitionEnd event did not fire after transition was complete (after 1s). Expected results: transitionEnd event should fire unrelated to computed style properties being changed. As workaround I use translate by 0.01px right now. See test case: http://jsfiddle.net/EykD5/
Summary: transitionEnd event doesn't fire if CSS property did not change during the transition → transitionEnd event doesn't fire if CSS properties did not change during the transition
> Apply transition with duration >= 0 to an element The attached testcase doesn't have any transition happening, because transitions are triggered by changes in computed values and no computed values change in the testcase. That behavior is required by the spec and is the same in WebKit as far as I can tell... > transitionEnd event should fire unrelated to computed style properties being changed. That's not what the transitions spec says.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
> That's not what the transitions spec says. That's true but it doesn't make much sense to me. Every JS-based animation engine handles it differently so you can count on callback being called. This is especially important for transitions defined programmatically. I'm not sure where to discuss this issue.
Transitions aren't animations. There's a totally different animations module in CSS. Discussion about CSS specs happens on www-style@w3.org.
You need to log in before you can comment on or make changes to this bug.