I encountered the same problem when I upgraded to 1.2.6 and using
"rowspan" instead of "rowSpan" fixed it. I guess it was a bug fix.
On May 27, 1:27 pm, snobo <[EMAIL PROTECTED]> wrote:
> Since upgrading to 1.2.5 (the same applies to1.2.6), an attempt to $
> ('... td').removeAttr('rowSpan') triggers an error in IE6/7.
> Previously (up to 1.2.4b) it effectively setrowSpanto 1. It still
> works that way in FF.
>
> I'm not sure is it a bug or a feature, but of course it has broken my
> application, so... I guess it should be either fixed or explicitly
> noted in the docs. I wonder, will it cause the same problem for some
> other attributes?
