See also #2408

#8830 is a duplicate of this ticket.

#2408 is a duplicate of this ticket.

Let's get this on the roadmap for 1.7.

Nominating ticket for 1.7 discussion.

+1,

+1, +1 +1 +1 +1 +1

+1, Is someone volunteering?

Now on a 1.7 branch in the repo.

fb3647f6558fddd8f05416b8a166e66b117244c5

http://jsfiddle.net/timmywil/gqZL5/17/

+1, Sounds cool - let's go for it!

+1, this is really interesting, but I assume it only works when using the same animation for both directions?

MooTools has a "link" option when animations are stacked. There's "ignore", "cancel", and "chain".

Ignore - ignores any calls while animating

Cancel - Cancels the current animation, starts the next one from the current state (what you're seeing in the original fiddle I created for ajpiano)

Chain - Stack the next effect. The default jQuery behavior (rarely what you want).

This option is obviously really helpful. I've been working on porting the MooTools Fx constructor to power the jQuery effects mostly for this option (and I find them a little smoother in some browsers).

@timmywil - I'm not entirely familiar with the underlying jQuery.fx, but wouldn't it be better to do the state tracking there so it just works™ with all animations? (rather than changing a lot of code in the shortcuts like show and slideToggle)

Regardless, VERY happy to see this progress on your 1.7 branch. I'm using jQuery for most of my work these days and battling this has ladened my transition to jQuery with frustration :)

@rpflorence: jQuery fx has a different structure than Mootools, a structure I don't think we want to change. The options mentioned can be replicated in different ways in jQuery. Ignore might be similar to setting queue to false, chain as you said is the behavior of the jQuery queue (which has its own advantages I think), and cancel...well that wasn't really an option before unless you created your own animation that kept track of state. Finally, I think you're confused about what I've written. The code I've added and updated will work for all animations. The show function you see updated is not jQuery.fn.show, it's the show on the jQuery.fx prototype. Any property set to "show" or "toggle" will use this function and that is what we're talking about. Animations set to actual values are unaffected because we don't have to do any calculations for the user. Like I said before, you could already do before what is done in MooTools with a custom jQuery animation that sets values and keeps track of its own state. This will add that state tracking so that actual values do not need to be passed. I think what you're asking for in your last comment is really what I've already done. Anyway, I agree. This is something I've wanted jQuery to do since I first started using it as well.

+1, Obvs - also it seems like timmy's solution seems to cover the intended problem in the right spot...

#10015 is a duplicate of this ticket.

Animation state is tracked on toggled/stopped animations using the private data cache. Fixes #8685. See full commit message for more. Fixes #6641.

• Example: http://jsfiddle.net/timmywil/gqZL5/24/

• http://bugs.jquery.com/ticket/8685

• Check the completed timer has not been removed already so other timers do not get accidentally removed. Fixes #6641.

• Style edits, code reductions, and optimizations for the effects module

Changeset: 1878885fb7a09b65d95980a9b7dce2df2944e4f9

#10263 is a duplicate of this ticket.

We had a regression on this in 1.8.0 - I'm going to make sure to cover this in the units.

http://jsfiddle.net/cz4XM/1/

Seems that @timmywil fix works fine with @gnarf fiddle here. And it solve a big problem, really.

Keep track of a hiding state for toggle based animations - Fixes #8685

Closes gh-1018

Changeset: c45f6095f2d58a9fefd6bc788e50140acc7cf0c4

Keep track of a hiding state for toggle based animations - Fixes #8685

Closes gh-1018

(cherry picked from commit c45f6095f2d58a9fefd6bc788e50140acc7cf0c4)

Conflicts:

src/effects.js

Changeset: bee4d0307216292bb0e69b7431d054cf86bdfc43