Opened 13 years ago
Closed 13 years ago
#5539 closed defect (fixed)
dojo._Animation: onEnd fires twice and the delay is not respected
Reported by: | dante | Owned by: | Eugene Lazutkin |
---|---|---|---|
Priority: | high | Milestone: | 1.1 |
Component: | fx | Version: | 1.0 |
Keywords: | fx combine delay | Cc: | |
Blocked By: | Blocking: |
Description
when doing advanced animations, dojo.fx.combine somehow causes FF to ignore any delay: parameters.
the effect can be seen here: http://dojotoolkit.org/~dante/dojo.moj.oe/mojo.html
each of the ball nodes fades in on approx ~300ms delay higher than the previous node, and dojox.fx.combine(anims).play()'d ... in Safari and IE7, the effect is the desired result, but in FF, all the animations play in unison, regardless of delay: parameters. it is using the delay: value of the first animation only.
also interesting to note, dojox.fx.combine(anims).play(50) override's any delay: param set on that first animation, and uses delay:50 on all animations in Safari and IE7 ...
Change History (6)
comment:1 Changed 13 years ago by
comment:2 Changed 13 years ago by
Owner: | changed from Bryan Forbes to Eugene Lazutkin |
---|---|
severity: | normal → minor |
this seems to be working, but leaving open to address onEnd issue noticed.
comment:3 Changed 13 years ago by
Milestone: | → 1.1 |
---|---|
Status: | new → assigned |
comment:4 Changed 13 years ago by
Summary: | dojo._Animation does respect delay: in FF → dojo._Animation: onEnd fires twice |
---|
comment:5 Changed 13 years ago by
Summary: | dojo._Animation: onEnd fires twice → dojo._Animation: onEnd fires twice and the delay is not respected |
---|
comment:6 Changed 13 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
(In [12478]) refs #5539 - it doesn't actually appear to be broken (the ticket claim) though new unit test introduce new issue: onEnd is fired twice (or more?) for chained and combined animations. unit tests pass, but you will see a console.warn() you should otherwise not.