ansaurus

Question

Answer 1

+1 A:

Pointy 2010-08-26 11:57:25

Due to the way the logic is (and I agree the API doesn't say anything about this), passing just a function is equivalent to `.show("normal", func)`, so his current code is actually a 400ms animation.

Nick Craver 2010-08-26 12:04:09

Are you sure? It looks to me like the function passed as the "speed" argument will essentially be ignored. That code is kind-of confusing, however, so I could be wrong. I'm looking at the little "speed()" utility in jQuery, which *I think* will try to use the function as a lookup into the named speed array.

Pointy 2010-08-26 12:05:32

@Pointy - The easiest way is to test, you can see the behavior here: http://jsfiddle.net/nick_craver/7sr4b/ :)

Nick Craver 2010-08-26 12:09:31

Never mind Nick, you're of course correct :-) I still don't see how the function ends up being called, but whatever. (edit - oh I see it now, line 5682 or so right at the top of "speed()")

Pointy 2010-08-26 12:10:27

@Pointy - They key is here: http://github.com/jquery/jquery/blob/master/src/effects.js#L17 As long as speed is anything but 0 it gets translated to `.animate(effect, speed, callback)` and since it checks for optional params it works :)

Nick Craver 2010-08-26 12:13:33

+1 to your answer - whatever you can get away with...there isn't an overload that matches what he's calling in the API, so the fact that anything breaks, well that's ok...the documented functions work, this just isn't one of them.

Nick Craver 2010-08-26 12:14:58

You are indeed correct about the number of arguments - strange how it was working before adding jQuery UI however. Now added 'normal' as a argument and all is working well. Thanks.

Digital Rant 2010-08-31 08:24:14

ansaurus

tags:

views:

answers:

Adding jQuery UI breaks jQuery show()

related questions