Opened 9 months ago

Closed 9 months ago

Last modified 8 months ago

#21736 closed enhancement (fixed)

Update to jQuery 1.8.1 and jQuery UI 1.9 RC

Reported by: nacin Owned by: nacin
Priority: normal Milestone: 3.5
Component: External Libraries Version:
Severity: normal Keywords: has-patch
Cc:

Description

jQuery UI 1.9 hit release candidate status last week. jQuery 1.8.1 is due out this week. Let's be good citizens and push both into trunk now.

Attachments (1)

21736.patch (182.2 KB) - added by ocean90 9 months ago.
jQuery 1.8.1 Final

Download all attachments as: .zip

Change History (11)

In [21657]:

jQuery UI 1.9 RC.

Adds Tooltip, Menu, and Spinner.
Autocomplete depends on Menu.
Renames Effects files.

1.9 final is expected next week.
see #21736.

  • Owner set to nacin
  • Resolution set to fixed
  • Status changed from new to closed

In [21658]:

jQuery 1.8.1-not-quite-final. fixes #21736.

In [21660]:

Update old files array:

  • Remove old names for jQuery UI Effects files. see #21736.
  • Remove un-minified version of Jcrop and jQuery Color. see #21692, #20728.
  • Remove .dev.css and .dev.js. see #21633.

jQuery 1.8.1 Final

comment:4 follow-up: ↓ 7   ocean909 months ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

jQuery 1.8.1 final is there. http://blog.jquery.com/2012/08/30/jquery-1-8-1-released/

In [21658] jQuery.noConflict(); was removed, intentionally? I added it back in 21736.patch.

And shouldn't we rename the file to jquery.min.js?

  • Keywords has-patch added
  • Resolution set to fixed
  • Status changed from reopened to closed

In [21695]:

jQuery 1.8.1 final. Also restores jQuery.noConflict(). props ocean90, fixes #21736.

comment:7 in reply to: ↑ 4   koopersmith9 months ago

Replying to ocean90:

In [21658] jQuery.noConflict(); was removed, intentionally? I added it back in 21736.patch.

Good catch.

And shouldn't we rename the file to jquery.min.js?

We haven't renamed .js that include only the compressed source as some plugins and themes might directly load the .js original in production. For the files we have renamed, it isn't really an issue: it falls back to the uncompressed source. But if we don't include the uncompressed source, there's no fallback (and for something like jQuery, that could have particularly bad results).

[UT1017] - Testing for the presence of jQuery.noConflict();

In [22182]:

jQuery 1.9.0 final. see #21736.

In [22182], I clearly meant jQuery UI.

Note: See TracTickets for help on using tickets.