The bug fix release for 1.1 is now ready for all to use. There were a lot of weird behaviors that were discovered post-1.1 that needed to be remedied sooner, rather than later. If you were having any difficulties with the 1.1 release, please try this new release to see if your problems were solved.
It is highly recommended that you upgrade.
- Full Release (jQuery, Test Suite, Documentation)
- Build Files (Compile your own version of jQuery 1.1.1)
Every bug ever fixed with jQuery can be found on the main bug fixes list. The most important bug fixes, relevant to this release, are as follows:
- Setting the numerical value of a css property failed, for example: .css(”opacity”,0.5) (also occurred with zIndex, fontWeight)
- Calling $(…, jqobj) with a context of a jQuery object failed.
- Accessing a property on an element that doesn’t exist caused an error, for example: $(”#foobar”).attr(”id”)
- Calling .load() without a callback caused an error.
- You couldn’t cancel an event that was triggered using .trigger() or .click() (for example).
- .add()ing a single DOM element to a jQuery object was broken.
- Passing in undefined values to a $.post() caused weird errors to occur.
- Accessing child nodes within an example document didn’t work properly.
- jQuery.isFunction() was unable to reliably determine a function, in a cross-browser way.
- Triggering a .click() failed in IE.
- Triggered click handlers were executed twice in most browsers.
- A newline passed into $(”…”) caused Firefox to go into a never-ending loop.
- Calling $.post() without any data caused an error.
- Calling a descendant selector after a child selector caused strange results, for example: $(”ul > li ul”)
- Triggered events did not occur if an event handler was not bound for that event.