#21736 closed enhancement (fixed)
Update to jQuery 1.8.1 and jQuery UI 1.9 RC
Reported by: | nacin | Owned by: | nacin |
---|---|---|---|
Milestone: | 3.5 | Priority: | normal |
Severity: | normal | Version: | |
Component: | External Libraries | Keywords: | has-patch |
Focuses: | 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)
Change History (11)
#2
@
12 years ago
- Owner set to nacin
- Resolution set to fixed
- Status changed from new to closed
In [21658]:
#4
follow-up:
↓ 7
@
12 years 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
?
#7
in reply to:
↑ 4
@
12 years 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).
In [21657]: