jQuery 1.5.2

[duck_]

jQuery 1.5 was released today.

​http://code.jquery.com/jquery-1.5.js

​http://bugs.jquery.com/milestone/1.5

​http://bugs.jquery.com/query?type=enhancement&type=bug&type=feature&milestone=1.5

[c3mdigital]

Patch added

[markjaquith]

We'll get this in 3.2, early on. Too late for 3.1.

[jkudish]

+1 on this one, glad it's getting into 3.2

[ramoonus]

jQuery 1.5.1 (bugfix release) is planned for next thursday

[ramoonus]

jQuery 1.5.1 has been released yesterday.

[filosofo]

Related: #16508

[niallkennedy]

jQuery 1.5.1 diff against 1.4.4

[ramoonus]

oops

[demetris]

Updates jQuery from 1.4.4 to 1.5.1

[hebbet]

jquery 1.5.2 is now available:
​http://blog.jquery.com/2011/03/31/jquery-152-released/

[JDTrower]

Updates jQuery from 1.4.4 to 1.5.2

[demetris]

Updates jQuery from 1.4.4 to 1.5.2

[demetris]

JDTrower, you forgot the noConflict() bit we add at the end. :-)

[JDTrower]

You're right. I did. I was running a comparison between your diff and mine to figure out what was different. noConflict() slipped my mind to make sure I added it back.

[azaozz]

The patch looks good. However, did anybody test if it breaks something? Currently tracking several issues that came from updating jQuery and jQUI in 3.1, one quite annoying that can make the Edit Page screen unusable in IE7/8.

Perhaps some (light) testing is in order before even thinking of updating. Unfortunately there's not much automated tests that we can do on UI sortables, etc. so it seems it has to be done by hand. A good testing install would have 300-400 Posts, 300-400 Pages, 200-300 Tags and 200-300 Cats. Main things to test:

• All draggable, droppable, sortable elements work as expected on all pages.
• Everything on the Add/Edit Post/Page screens works as expected.
• Any bugs are reported on the jQuery and jQUI tracs.

Testing has to be done in all currently supported browsers: IE 7, 8, 9; FF 3.6, 4.0; Safari 5, Chrome 10, Opera 10.

[ramoonus]

and opera 11

[JDTrower]

I'm still planning on testing the other browsers, but have tested in FF 4.0 and the same problem reported on #16955 still occurs in 3.2-bleeding with jQuery updated to 1.5.2 with this patch.

[JDTrower]

Not sure how I got set to owner or how the status or component got changed, but trying to fix that now.

[JDTrower]

I have tested the latest patch in IE 7, IE 8, IE 9, FF 3.6, FF 4.0, Safari 5, Chrome 10, Opera 10, and Opera 11 on Windows Vista and Windows 7 computers and I didn't notice any bugs. Everything worked as expected. This was done on a test install with 311 posts, 387 pages, 216 categories, 408 tags, and 401 comments. Recommend that this can be committed.

[JDTrower]

Should have mentioned that IE 8 and 9, I did encounter problems that are listed in detail on #17070. But other than that ticket and #16955 (which the fix has been applied upstream and just waiting on the release of jQuery UI 1.8.12) everything else worked fine for me.

[demetris]

Thank you for you taking the time to do this, JDTrower.

By the way, nacin suggested the other day on the IRC channel that we should make a checklist for testing jQuery and jQuery UI updates. I think this is a good idea, as it would make testing better and easier: you open the checklist, launch the supported browsers, and you start going through the checklist point by point.

[JDTrower]

Replying to demetris:

Thank you for you taking the time to do this, JDTrower.

By the way, nacin suggested the other day on the IRC channel that we should make a checklist for testing jQuery and jQuery UI updates. I think this is a good idea, as it would make testing better and easier: you open the checklist, launch the supported browsers, and you start going through the checklist point by point.

You're welcome demetris.

I agree that that is a good idea. It would make testing not only better and easier, but also more consistent. I assume a checklist like that would be a Codex page or would it be located somewhere else?

[ramoonus]

1.6 beta 1 has just been released
more info @ ​http://blog.jquery.com/2011/04/15/jquery-16-beta-1-released/

[hebbet]

jQuery 1.6 is currently planned for end of April.
Feature freeze of Wordpress 3.2 is schedueled for April 30, so i think it is too late for getting jQuery 1.6 into Wordpress 3.2

[scribu]

@JDTrower: Yes, a Codex page would be a good start.

@ramoonus: jQuery 1.6 doesn't sound like a good idea for WP 3.2.

[ramoonus]

i know its slightly offtopic
but i have developed a very simple plugin ( ​http://wordpress.org/extend/plugins/jquery-updater/ )
which replaces the default WP jQuery with the latest stable version
but only for the front-end
ideal for testing your websites content with a "future" WP jQuery version

[azaozz]

(In [17725]) jQuery 1.5.2, props JDTrower demetris, fixes #16426

[azaozz]

In [17777]:

Add quotes to [value="some"] selectors, see #16426

[scribu]

For jQuery 1.6: #17311