Update jQuery & UI to the latest git versions available (currently 1.6.3pre & 1.9pre respectively)

It would be great to stay up to date with jQuery on a rolling basis in Drupal 8, but this is a task rather than a bug.

For Drupal 7, the jQuery version is frozen after release, http://drupal.org/project/jquery_update handles this for Drupal 7 and earlier.

#1085590: Update to jQuery UI 1.9

Subscribing here too ...in case it is decided that #1085590: Update to jQuery UI 1.9 will hold stable releases of jQuery and here's where one will find the latest "bleeding edge" versions.

As discussed in #1085590: Update to jQuery UI 1.9, these are not duplicate issues. That issue aims to get Drupal 8 up to the latest released version of jQuery. This issue aims to closely track jQuery git. The two issues can be debated on their own merits.

...just some 'minor' edits in the issue's title so that one knows at a glance what versions the latest patch includes.

@keichee: hope you don't mind the extra work of keeping the title up to date as well Lauro ;)

PS: can we hope for a D7 patch here along with the D8 (against latest 7.x-dev)?

@klonos: we can't upgrade the version of jQuery that D7 ships with because it would be a bc break in Drupal core itself. jQuery update module handles that for stable releases.

sorry, offtopic,
old version of jQuery gives really bad imagine to developers.

eg.

Don't want Drupal 6 or 7 to slow down a Drupal 5 site? Deal with an outdated jQuery. For most sites that's fine. We really care about speed because Google and Microsoft have demonstrated that users are more loyal to fast sites. In 2009, when Drupal 6 was out and established, we stuck with Drupal 5 because of the measurable speed advantage. The problem is that Drupal 5 includes jQuery 1.0. You can add a contributed module to patch jQuery to 1.2 (and update the Drupal functions that reference it), but that's still an old version. Forget about jQuery 1.3x and Drupal 5.

http://erickennedy.org/Drupal-7-Reasons-to-Switch

Yes, it can use jQuery Update sometimes, sadly other modules won't support new version of jQuery, there is a big deal.

for now, clearly it can't add new version of jQuery into CORE. IMO, it can be move this issue to jQuery Update. That may help to speed up the releases. 1.6 is released about 2months but jQuery Update is delivery 1.5.x only.

Unit and functional testing of core's JavaScript would make it easier to consider jQuery updates in core.

However even with that droplet's point still stands - if modules are written to work with Drupal 7.0, they also need to work with Drupal 7.20 (except in rare cases where a critical bug forces an API change, but that's quite rare). The last time I looked at a jQuery changelog (which was quite some time ago), bug fixes, new features and bc breakage were all mixed in to a minor point release.

Since we can expect numerous minor and major releases to come out during the entire lifecycle of a core release (Drupal 6 will be supported for another couple of years), it's not just one bc change either (like a critical bug might be) - modules that have JavaScript might need to be upgraded several times. Not to mention custom JavaScript on sites which might break etc. etc.

Having said that, both Dries and webchick have said they're opening to considering some limited new features for Drupal 7 (now that we have automated testing for PHP this is easier). So if there was a more recent jQuery release which claimed to have no bc breakage, updating might not be out of the question - but in practice if previously working code breaks, this is very unlikely to happen.

It might worth opening another issue (I know I keep recommending splitting issue, but that's the easiest way to get things done in core - one thing at a time), to discuss reconsidering this for Drupal 8. For example moving some aspects of jQuery update or libraries module into core - although there may already be issues open for this. That might allow for example shipping both the 7.0 and latest stable jQuery and jQuery UI versions with core, defaulting to the new one for new installs, but leaving the old one in place on sites that are upgrading (who could change it manually when they wanted to).

Overall there are a lot of things to consider with changes like that - mainly contributed and custom modules - other than whether just core could keep up by itself.

I don't know about jQuery update in core. It sounds good except the release cycle being slow and all. OTOH, if Libraries API was to get in core + let it handle jQuery, then we could a) allow end users to easily update jQuery independently from core - no patches involved b) allow them to revert to a previous known-to-be-working version in case of bc breakage c) perhaps find a way to let various modules use different versions of jQuery through Library API and some kind of magic.

It's not critical, and I doubt git versions of jquery will ever get committed to core (too likely to cause breakage, too much ongoing effort for core committers, etc). #1085590: Update to jQuery UI 1.9 has much more chance of success.

This is really won't fix - core is never going to contain git based versions of jquery we need a version to develop against during a drupal cycle.

jQuery UI 1.9 is right around the corner. We should update to the latest in git to help the jQuery UI team out with their upcoming release, and allow us to start using some of jQuery UI 1.9 in Drupal core.

Whoops, wrong thread, meant to point people over to #1085590: Update to jQuery UI 1.9.