Hi, can you provide a reduced test case using jsFiddle.net? We don't have enough information to determine if there is a bug.

Most likely the newMaxHeight value is non-numeric in the case where IE is throwing the error. Use a debugger (Firebug in Firefox, Ctrl-Shift-I in Chrome, F12 in IE) to stop execution at that point in your code and examine the arguments to animate().

As previous stated, this only occur in IE with 7 standards.

I've already debugged this segment, and I can definitely that newMaxHeight is numeric.

As for reduced test case, that would be difficult, but I would try.

I might be able to narrow it down:

The error is thrown from this line - a.elem.style[a.prop]=(a.prop==="width"||a.prop==="height"?Math.max(0,a.now):a.now)+a.unit

that's what IE is referring to.

Checking it further, it seems that a.now is: "noneNAN". Other than that: a.prop is maxHeight and a.unit is "px".

Call stack is:

> _default

update

step

h

custom

Anonymous Function

dequeue

Anonymous Function

each

each

queue

animate

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!

I am having a similar "Invalid argument" issue with XP / IE8 Standards / jQuery 1.6.2 - there seems to be a race condition earlier in the call stack which results in variable fx.now at line 8538 intermittently taking values such as 'NormalNaN', '#444444NaN, etc., depending on which property is being animated.

Unfortunately I am not sufficiently familiar with the internals of jQuery to readily spot where this arises.

same for me, on IE7 i got an "no valid argument" in line 8538 of jQuery 1.6.2

seem coming from this line :

fx.elem.style[ fx.prop ] = (fx.prop === "width" || fx.prop === "height" ? Math.max(0, fx.now) : fx.now) + fx.unit;

Bug is still reprodusible.

i am still getting this bug in IE7 and IE8

i am using .css('min-height', VALUE) with a numeric value without 'px' for resizing the main-div on page-load

Please stop posting the "I am still getting this bug" comments and post a test case we can use to diagnose. I'll reopen the ticket in anticipation of a reply.

I see people asking if newMaxHeight on the op snippet is numeric. Even if its not, it doesn't really matter because it gets concatenated with "px", so it becomes a string.

I can confirm that I get this error only when I'm passing in 0 (zero) with a unit as an argument. For example:

// Fails
$("#foo").animate({ marginLeft : "0%" }, "fast");

// Works
$("#foo").animate({ marginLeft : "0" }, "fast");

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!

Similar fix

Has error:

$(this).animate({top: '=0'}, 105);

Works:

$(this).animate({top: '0'}, 105);