Side navigation
#9789 closed bug (wontfix)
Opened July 09, 2011 06:11AM UTC
Closed July 09, 2011 04:04PM UTC
If an animation 'complete' callback throws, it will keep getting invoked repeatedly
| Reported by: | anonymous | Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | 1.next |
| Component: | effects | Version: | 1.6.2 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
See https://bugzilla.mozilla.org/show_bug.cgi?id=669107#c4
Basically, if a 'complete' callback throws, its corresponding animation will keep going, and any later animations won't be processed correctly at all.
Attachments (0)
Change History (1)
Changed July 09, 2011 04:04PM UTC by comment:1
| component: | unfiled → effects |
|---|---|
| priority: | undecided → low |
| resolution: | → wontfix |
| status: | new → closed |
This cannot be changed unless we want to go back to the old queue order. However, if callbacks do not throw errors (which they shouldn't after debugging), everything works fine so I'm not sure having a disordered queue is worth the fix. Ideally, we could use a try {} finally {}, but this causes problems in IE if there's no catch (which we can't add for debugging reasons). And setTimeout(f, 0) would be unpredictable. If we want to maintain consistent behavior across browsers, it should probably stay as is.