Skip to main content

Bug Tracker

Side navigation

#9100 closed bug (fixed)

Opened May 04, 2011 03:58PM UTC

Closed May 10, 2011 03:26PM UTC

Order of hide() callbacks has changed

Reported by: Odilon Redo Owned by: lrbabe
Priority: blocker Milestone: 1.6.1
Component: effects Version: 1.6
Keywords: Cc:
Blocked by: Blocking:

The order in which callbacks for hide() are processed has reversed in 1.6 - previously (e.g. in 1.4,1.5) the callbacks would fire in DOM order (e.g. 1,2,3 in the code below) but they now fire in reverse (3,2,1). This behaviour is tested in Firefox 3.6.17 and Chrome 10.0.648.205.


<div id="div1">1</div>
<div id="div2">2</div>
<div id="div3">3</div>

<script src=""></script>






Attachments (0)
Change History (5)

Changed May 08, 2011 07:15PM UTC by addyosmani comment:1

component: unfiledeffects
priority: undecidedblocker
status: newopen

Confirmed as a regression: As mentioned the order changes between 1.5.2 and 1.6.x with the issue still being present in our current edge.

Changed May 08, 2011 07:19PM UTC by jaubourg comment:2

milestone: 1.next1.6.1

Changed May 09, 2011 01:13PM UTC by lrbabe comment:3

owner: → lrbabe
status: openassigned

Changed May 09, 2011 03:40PM UTC by lrbabe comment:4

Changed May 10, 2011 03:26PM UTC by louisremi comment:5

resolution: → fixed
status: assignedclosed

Landing pull request 374. .animate() Callbacks should fire in correct order (unit test included). Fixes #9100.

More Details:

Changeset: 521ae562daa8f95def8872a55a260e9bdbc40d8b