jQuery 1.7.1 Released

Here in the United States, we’re celebrating Thanksgiving this week. For those of you living elsewhere in the world, it’s a time when we install and test new versions of Javascript libraries while feasting on Mom’s homemade goodies. Kind of like a code sprint, but with better food. We invite everyone worldwide to join us in these traditions.

To kick off the festivities, the jQuery Team is quite thankful to be releasing version 1.7.1! In this go-round we made Pilgrim’s progress on a cornucopia of bugs, listed below. We are serving up our delicious copies on the jQuery CDN, fresh and warm from the oven:

These latest files should also be up on the major CDNs shortly, but please be patient since this is a holiday week for them as well.

Please install and test this latest slice of jQuery with your code. We hope you’ll find it tasty. If we forgot to fry some turkey of a bug, we want to hear about it. Just put together a specific test case for the problems you’ve found (we love jsFiddle.net for that) and create a bug report at bugs.jquery.com.

Also, please welcome new jQuery Core team member Mike Sherov! We’re thankful to have his help for all the great things we have planned for upcoming versions. Mike has a full-time job at SNAP Interactive in New York City, but contributes to the project in his spare time. Please Be Like Mike and pitch in to help the project any way you can. It doesn’t have to be coding. We can always use help in answering questions on the forum or just reproducing and identifying the source of obscure bugs reported on the bug tracker. See our Getting Involved page for information.

We’ll be opening the call for 1.8 suggestions in just a day or two. Take a look at the 1.7.1 release and think about what kind of awesome sauce we can put on top of it for the next big one!

I had an issue on IE with jQuery returning an error for a missing argument.
It was caused by a call $(element).show() after a $(‘document’).ready().

I fear IE completely misses to pass some element feature (width? display status? visibility status?), or in some way those features are not readable to IE, or become available slight AFTER the .ready() is called.

you make this to difficult to use it would be nice to just go to a page and click on a button and download what I want there is no need to go through all the other stuff and still not find what I am looking for.

ERROR:”event.layerX and event.layerY are broken and deprecated in WebKit. They will be removed from the engine in the near future.”

thank you so much jquery developer… the same thing that error i received from previews version jquery-1.4.2 in Chrome, i thought the error occur is from my own program code… so i try to fixed but still the same, then i quit! :D

thanks God I found the solution…
I’m using jquery to provide perfect animation effects,
it made my works easier and understandable..

@stc – The reason you prefer 1.2.6 is because it was the stable release for so long. I actually prefer 1.3.2 for the same reason.

Now it seems like my favorite software products are releasing updates every few weeks instead of letting stuff simmer for a bit. This seems to be the result of the GitHub mentality/craze – too much churn, not enough testing. “Let the guinea pigs report issues to the issue tracker and push fixes to me…there is no need to actually test what I release.” GitHub is the ultimate tool for lazy software developers.

Several people are saying IE is broken with this release. IE still powers half of the browsers out there. Most web developers I encounter view those users as unenlightened. Whatever. You target the largest common denominator and test the heck out of it regardless of your personal feelings and preferences. That might mean, shock of all shocks, actually using IE to develop software!

Wanted: A single webpage where I can go and get a changelog of what has changed in every release for jQuery.

I would like to know whether I can make jquery 1.7.1 work with jquery 1.5.2 tried replacing the 1.5.2 with 1.7.1 didn’t work at all. Looking forward to some of your suggestions on how to make it work without affecting the site functionality. Thanks

One of my pages is rendered completely blank when I use 1.7.1 version and when I replace it with 1.6.4 and older version, it works fine.
I am trying to find the solution since more than a week now. I don’t want to downgrade to a lower version. Can someone please help me with this?