Opened 12 years ago
Closed 12 years ago
#9100 closed bug (fixed)
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: |
Description
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.
<body> <div id="div1">1</div> <div id="div2">2</div> <div id="div3">3</div> <script src="http://code.jquery.com/jquery-1.6.min.js"></script> <script> $("div").hide(1,function(){ console.log($(this).attr("id")) }); </script>
</body>
Change History (5)
comment:1 Changed 12 years ago by
Component: | unfiled → effects |
---|---|
Priority: | undecided → blocker |
Status: | new → open |
comment:2 Changed 12 years ago by
Milestone: | 1.next → 1.6.1 |
---|
comment:3 Changed 12 years ago by
Owner: | set to lrbabe |
---|---|
Status: | open → assigned |
comment:5 Changed 12 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Landing pull request 374. .animate() Callbacks should fire in correct order (unit test included). Fixes #9100.
More Details:
Note: See
TracTickets for help on using
tickets.
Confirmed as a regression: http://jsfiddle.net/bEMRy/3/. As mentioned the order changes between 1.5.2 and 1.6.x with the issue still being present in our current edge.