Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
jQuery UI 1.8.5 is out. We should update the library to the newer version.
Comment | File | Size | Author |
---|---|---|---|
#41 | changelog-916968_41.patch | 766 bytes | xmacinfo |
#37 | jquery-ui-1.8.6_916968_37.patch | 447.75 KB | amateescu |
#32 | jquery-ui-1.8.5_916968_32.patch | 446.43 KB | amateescu |
#28 | jquery-ui-1.8.5_916968_28.patch | 447.05 KB | amateescu |
#19 | jquery-ui-1.8.5_916968_19.patch | 447.73 KB | mfer |
Comments
Comment #1
marcvangendWhy is this critical?
Comment #2
oriol_e9gBecause we have to do this now or possible never in D7
Comment #3
marcvangendCurrently, D7 is not broken because jQuery UI 1.8.5 is missing. According to http://drupal.org/node/45111, "Tasks and Feature Requests should never be marked 'critical'." This is major at best. If we keep marking stuff like this as critical, D7 will never be finished.
Comment #4
mfer CreditAttribution: mfer commentedI'm marking this as critical because it is considered a bad idea to launch a new version of Drupal with an outdated version of a library like this. Critical items are release stoppers. Releasing a version of Drupal (7.0 release) with a version of jQuery UI that has had bug fix releases that we did not incorporate is a bad idea.
When we have released Drupal in the past it has been with the latest jQuery releases. We need to continue that trend.
Comment #5
Bojhan CreditAttribution: Bojhan commentedIf you think its so critical supply a patch please.
Comment #6
mradcliffeJust posting some reference material.
There have been many bug fixes with the five releases since 1.8.0 was patched for Drupal in #679036: Upgrade to jQuery UI 1.8. Many of these look important for UI developers to be aware of, but not security-related. Changelog links:
Comment #7
Jackinloadup CreditAttribution: Jackinloadup commentedWill it be possible to upgrade jQuery UI minor releases after D7 is released?
Comment #8
drifter CreditAttribution: drifter commentedWell, here's an attempt. Replaced the jquery.ui files to their 1.8.5 equivalent, and updated system.module with the new version numbers.
Comment #9
mfer CreditAttribution: mfer commented@drifter I'll take a look at this. Thanks for the patch.
@jackinloadup I cannot say if core will update the version of jquery ui shipped. If not, there will be a contrib module to do so.
Comment #10
marcvangendDo the automated tests cover javascript changes like this, or do we need to change this manually?
Comment #11
Jeff Burnz CreditAttribution: Jeff Burnz commented@#7, maybe we'll need a jqueryui_update.module? Sub_scriben....
Comment #12
jrabeemer CreditAttribution: jrabeemer commentedThis patch will go in if there's enough testing. Drupal isn't going to beta for 3-4 weeks so there's plenty of time to test.
Comment #13
drifter CreditAttribution: drifter commentedAlso: not critical. Nothing is broken. Read through the JQuery UI changelogs and commit messages, couldn't find anything major.
Update modules will be provided in contrib anyway, as they have existed in the past.
Would be nice to include this, but definetly not critical.
Comment #14
mfer CreditAttribution: mfer commented@drifter Critical issues are release blockers. Drupal 7 should not ship without being on the latest 1.8.x release. There are bugs in jQuery UI that may creep into sites we will build.
@marcvangend The automated tests cover the PHP handling of JavaScript but that's all. The way JavaScript interacts in a page, the animations, etc. are not tested. It is a product of the type of system we are using. So, JavaScript functionality is still manual for the time being.
@Jeff Burnz jQuery UI updates, after the D7 final release will happen through either the jquery_update module or the jquery module. We are still working on the plan for this in D7.
Now, on to the patch. There were a few more changes than just a simple swap of files.
The attached patch makes these changes. I tested in Safari and Chrome where everything seemed to work.
Comment #16
ksenzeeI know this feels like it should be a release blocker, but I honestly don't think it is. We can fix it anyway though.
Besides the patch not applying (because of a problem with jquery.ui.selectable.css), I'm seeing a couple more problems:
- @VERSION appears in several files instead of 1.8.5. This might be an upstream problem, but we should get it fixed before we add it to our codebase and cause all kinds of confusion.
- We're overwriting a lot of existing $Id$ strings that are already in CVS.
Comment #17
webchickYeah. This isn't a major version change in jQuery UI, so there's no reason we couldn't roll this out in 7.1 or 7.2. No reason for it to block release. Hopefully it's ready well before that becomes an issue though. ;P
Comment #18
webchickOh, and yes, manual is the only way with JS. :\ Although it's tricky to test this with just core, since afaik nothing in core actually uses jQuery UI...
Comment #19
mfer CreditAttribution: mfer commentedA patch that should work. Also note, The file misc/ui/images/ui-anim_basic_16x16_0.gif is not loger part of jquery ui and needs to be removed.
Comment #20
sunThis patch cannot be tested, but it's OK to commit it.
We should not change CHANGELOG.txt.
Actually, all JS files should use the former variant.
That said, I wouldn't mind to have no $Id$ CVS keywords in those files. We do not and will not change them on our end. So as long as they contain the proper version, there's no benefit of manually injecting a CVS Id tag. Would heavily simplify updates like this.
Still contains plenty of @VERSION placeholders? I guess this means that this has to be fixed upstream.
Powered by Dreditor.
Comment #21
mfer CreditAttribution: mfer commented@sun Ideally we would just use the files from jQuery UI directly rather than modifying them.
Comment #22
jrabeemer CreditAttribution: jrabeemer commentedSub
Comment #23
bojanz CreditAttribution: bojanz commentedWhy not skip the $Id$ tags?
They will disappear anyway as soon as the Git migration happens (a script will go through all source and strip it), and that time is approaching fast.
Comment #24
Jeff Burnz CreditAttribution: Jeff Burnz commentedI think we have to have revision control on this file because there are modifications to it, as opposed to the core ui theme css which is a strait copy (correct me if I am wrong, not totally up with this issue).
Comment #25
webchickThis didn't make it into beta1, but it'd be nice to make into beta2. Any takers?
Comment #26
marvil07 CreditAttribution: marvil07 commentedAs mentioned on the release blog post, some versions include @VERSION string. I suppose the problem was from where it was downloaded. So I think there is no a problem upstream(where I can see the right version).
@webchick: what is the official position about $Id$ ? (I suppose it is to include them, but I also think it is unnecessary since we do not touch them)
Comment #27
jrabeemer CreditAttribution: jrabeemer commentedLooks like this may not make it in before release.
Comment #28
amateescu CreditAttribution: amateescu commentedThis patch addresses sun's comments in #20.
Comment #29
amateescu CreditAttribution: amateescu commentedComment #30
sunNow is the perfect time to do this. Sufficient time to find any obscure bugs until the next beta/RC.
Comment #31
mfer CreditAttribution: mfer commentedAccording to the JavaScript Coding Standard the header blocks on JavaScript files should be in the form
// $Id$
@VERSION should be replaced by 1.8.5. This is all over the code.
Powered by Dreditor.
Comment #32
amateescu CreditAttribution: amateescu commentedI replaced all the js headers, and the @VERSION string was only in autocomplete.css because i manually replaced all the others in the first patch :) I guess this one slipped because it wasn't at the beginning of the file...
Comment #34
mfer CreditAttribution: mfer commentedThe failure should not be related to this patch. Did a failing test get in?
Comment #35
darvit CreditAttribution: darvit commentedUpdated point release for jQuery UI :
jQuery UI 1.8.6 has been released today.
http://code.google.com/p/jquery-ui/downloads/detail?name=jquery-ui-1.8.6...
Comment #36
lilou CreditAttribution: lilou commentedhttp://jqueryui.com/docs/Changelog/1.8.6
Comment #37
amateescu CreditAttribution: amateescu commentedNew patch for jQuery UI 1.8.6.
Comment #38
marvil07 CreditAttribution: marvil07 commentedlooks good, just to point the comment of mfer at #19: #916968-19: Update to jQuery UI 1.8.6, so we do not forget about that remove
Comment #39
webchickI was about to commit this, but where on jQuery's site do you see 1.8.6?
http://jqueryui.com/download shows 1.8.5 as "stable" to me?
Comment #40
webchickHm. I guess they have a GitHub tag and Google's CDN version is pointing at 1.8.6. I asked in #jquery and they told me 1.8.6 is indeed the latest, just awaiting a release announcement. I know a little something about that situation. ;)
Committed to HEAD.
Comment #41
xmacinfoChangelog patch specifying the new version of jQuery UI ready for review.
Comment #42
xmacinfoBy the way, #944308: Update to jQuery 1.4.4 had a changelog modification for jQuery. This is why I created a modification to the changelog for jQuery UI as well.
Comment #43
webchickCommitted to HEAD. Thanks.
Comment #45
darvit CreditAttribution: darvit commentedAnother updated point release for jQuery UI:
http://blog.jqueryui.com/2010/12/jquery-ui-1-8-7/
Changelog:
http://jqueryui.com/docs/Changelog/1.8.7
Comment #46
geekgirlweb CreditAttribution: geekgirlweb commented+1 subscribing
Comment #47
neclimdulThis is really completed. We're not going to drag this issue out with every point release of jQuery UI.
#1009862: Update to jQuery UI 1.8.7