jQuery 1.0.3

Another bug-fix release is ready for all to enjoy! It is highly recommended that you upgrade right away. As always, if you spot a bug, please add it to the bug tracker.

As with the last release, jQuery 1.0.3 is featuring only bug fixes – leaving all API additions/changes/deletions until the next full release: jQuery 1.1.

Once again, JÃ¶rn Zaefferer did an incredible job really keeping on top of the bugs, fixing the vast majority of them. Much of this release was made possible by him.

Download Now:

This release includes a new package: A complete zip file of everything associated with this release. This includes three versions of jQuery (Regular, Lite, and Packed), the test suite, and all the documentation. Now you don’t have to build it yourself just to have your own copy.

Tickets Closed:

The full set of bugs, or enhancements, that were closed with this release:

Note: Even though about 60 bugs are shown below, many of them were messed with by spammers – so I’m not entirely sure which ones were fixed this release and which ones are just zombie bugs that got re-closed. I’m fairly positive that while there were a lot of bug fixes this release, there weren’t 60 of them.

Thanks for suggestion,John,so you say XmlHTTPRequest available only for generic ajax requests? $.get,post,load are out of luck?It’s not very consistent for framework,don’t you think?And if you accept that I say,why put such constraints in the first place?

By the way,why $.ajax has success/complete/… separation but other ajax functions dosen’t?So,I have to use function(xml,status){} signature all the time and check for “success” myself using “status”.Could you,please,provide more consistent programming model for ajax requests?

It looks like a lot of bug fixes, but unfortunately I can’t upgrade. Whatever has changed has caused the tabs plugin to not work correctly in IE. I’d submit a bug report, but I have no idea on what the problem might be.

Small bug(feature)-if you’are using saveHistory behavior(very useful feature for “form” element) of IE-getAttribute/setAttribute methods are “blocked/overrided”,hence $().attr() dosen’t work at all.You have been warned;-)

Found a bug with using hover event binding in IE. Memory keeps spiking whenever i hover over any elements that went through the hover binding process. Also noticed that the IE memory leak hasn’t been addressed yet. (Memory leak whenever the page refreshes)

If you have enough control over your page to worry about performance, you can just avoid including jQuery more then once, therefore preventing any performance issues. The check is necessary for cases where you don’t have that control.

@all bug reporters:

Could you please use the bug reporting (http://jquery.com/dev/bugs/new/) to post bugs? Thats helps a lot to keep thing organized and getting them done. Thanks!

I wanted to let you know that it seems Jquery is having a conflict with the latest Mootools library. I am not a .js script kiddie at all, but I noticed that if mootools is activated AFTER JQuery, then it cuases issues with scripts written in JQuery. I am a Joomla developer and have created 2 extensions in my demo site at http://demo.joomlaworks.gr, the one uses JQuery (the Header Rotator) and the other (Simple Image Gallery) uses Mootools.

Changing the order of the scripts solves the problem. I tried various activations/deactivations with both libraries and it seems that the problem is only with JQuery.