#17952 closed task (blessed) (fixed)
Update to latest jQuery and UI
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | normal | Milestone: | 3.3 |
| Component: | External Libraries | Version: | 3.2 |
| Severity: | normal | Keywords: | needs-patch |
| Cc: | ramoonus@…, jpenney@… |
Description
jQuery 1.6.2 was released today.
Attachments (1)
Change History (29)
- Keywords 3.3-early added
- Milestone changed from Awaiting Review to Future Release
We'll drop this into trunk right after we branch. If things don't break then 3.2.1 is possible.
- Keywords 3.3-early has-patch removed
- Owner set to azaozz
- Status changed from new to reviewing
- Summary changed from Update to jQuery 1.6.2 to Update to latest jQuery and UI
The update to jQuery 1.6.1 brought quite a few plugin/theme issues despite that we did everything possible to warn plugin and theme authors. Perhaps we should update both jQuery and UI in August and stick with them for 3.3.
Closed #17474 as duplicate.
Replying to jczorkmid:
For compatibility's sake this is a good idea. Was hoping we would move away from UI in core as we mostly use it for drag+drop support and there are lighter jQuery plugins for this.
However it seems many WordPress plugins and themes will continue to use UI, so adding the whole UI to core will make it easier for them. The only "against" would be the increase of the total download size of WP.
On the other hand we probably could un-bundle Prototype.js as very few plugins seem to use it. Perhaps we can leave it in script-loader but load it from Google.
Replying to azaozz:
The update to jQuery 1.6.1 brought quite a few plugin/theme issues despite that we did everything possible to warn plugin and theme authors. Perhaps we should update both jQuery and UI in August and stick with them for 3.3.
true but was 1.6.1 or 1.6 to blaim?
i think 1.6
comment:10
in reply to:
↑ 8
;
follow-up:
↓ 11
jczorkmid — 22 months ago
- Cc jpenney@… added
comment:11
in reply to:
↑ 10
azaozz — 22 months ago
comment:12
follow-up:
↓ 13
jczorkmid — 22 months ago
Ok, thanks. Hopefully they won't just grab the latest. The patch also added the remainder of the UI libraries to wp-includes/script-loader.php. :)
comment:13
in reply to:
↑ 12
ramoonus — 22 months ago
errrrrrrr
comment:14
ramoonus — 22 months ago
jQuery UI 1.8.15
http://blog.jqueryui.com/2011/08/jquery-ui-1-8-15/
comment:15
ramoonus — 21 months ago
jQuery UI version 1.8.16
http://blog.jqueryui.com/2011/08/jquery-ui-1-8-16/
comment:17
follow-up:
↓ 18
marcelometal — 21 months ago
I updated WP for use jQueryUI >= 1.8.13 and an error occurred when using a new widget in the sidebar.
In wp-admin/js/widgets.js, line 113:
var add = ui.item.find('input.add_new').val(),
n = ui.item.find('input.multi_number').val(),
id = ui.item.attr('id'),
sb = $(this).attr('id');
'id' is undefined, because it was removed from ui.item
comment:18
in reply to:
↑ 17
azaozz — 20 months ago
Replying to marcelometal:
Yes, this is a regression. Still wondering what's better: patch that and update to 1.8.16 or keep 1.8.12. Opened a ticket on UI's trac: http://bugs.jqueryui.com/ticket/7734
comment:19
follow-up:
↓ 21
nacin — 20 months ago
Would rather patch and update to 1.8.16, but still track this upstream. Thanks for submitting.
comment:20
azaozz — 20 months ago
In [18757]:
comment:21
in reply to:
↑ 19
azaozz — 20 months ago
Replying to nacin:
Yes, added a workaround for that, preferable to changing it. Hopefully it will not break anything else as combining Draggable with a Sortable is not common.
comment:22
Viper007Bond — 20 months ago
Glad to see the full jQuery UI library rolled in.
comment:23
follow-up:
↓ 24
azaozz — 20 months ago
In [18774]:
comment:24
in reply to:
↑ 23
nacin — 20 months ago
Replying to azaozz:
single instance widgets (do they still exist?)
They're all over the place, for sure.
Akismet even still uses them.
comment:25
nacin — 20 months ago
In [18795]:
comment:26
ryan — 20 months ago
- Type changed from enhancement to task (blessed)
comment:27
ryan — 20 months ago
- Resolution set to fixed
- Status changed from reviewing to closed
Resolving as fixed. We can open a new ticket if and when the jui regression is addressed upstream.
comment:28
Anton Torvald — 19 months ago
Nothing.

maybe for 3.2.1