jQuery UI 1.8

[ocean90]

For some days ​jQuery UI 1.8 is published. We should update it in the core too.

For 3.0 I think its to late, so maybe 3.1.

• ​Changelog
• ​Changes between 1.7.2 and 1.8

When we do this, we should replace our autocomplete jQuery plugin with the new jQ UI one (which is built on top of the one we're using).

I'm seeing jQuery UI Tabs broken in the current 3.0b2. When testing by updating jQuery UI Core to 1.8.1 and updating the jQuery UI Tabs to 1.8.1 it works.

It'd be nice if this was remedied in 3.0, but I can de-register the Core and Tabs and include the latest for the plugin I'm writing for a client if that's not possible.

Kicking the Milestone back to 3.0, and setting Type to "bug", to let someone review and decide if it needs to be fixed in 3.0 or 3.1

There's no time to retest everything for 3.0. We'll get this early 3.1.

1.8.4 has been released a day or two ago.

jQuery UI update from 1.7.3 to 1.8.5

Though barely qualified to be making this patch, I thought it would be good to have it in sooner than later, so I tried my hand at it.

I am running it on two different setups and haven’t noticed anything broken yet.

I think this needs a lot of testing. And we don't have any tests for it as far as I remember. So good to have a patch now!

(In [15711]) jQuery UI 1.8.5. Props demetris. fixes #12863

I find that [15711] breaks all widget functionality. After applying this changeset, widgets can no longer be created using drag-and-drop (non-accessibility mode). Any time a new widget is dragged into a sidebar location, the following error is generated:

uncaught exception: cannot call methods on draggable prior to initialization; attempted to call method 'destroy'

This changeset should be reverted until proper testing can find and correct this issue.

Correction. I said in my previous comment "breaks all widget functionality". I meant to say that changeset [15711] breaks all widget creation functionality. Removing, modifying, and reordering widgets works as expected.

A quick search tells me that the issue is specific to jQuery UI v1.8.5. It did not exist in v1.8.4 and it is fixed in v1.8.6 (not released yet).

More: ​http://dev.jqueryui.com/ticket/6069

Replying to chrisbliss18:

This changeset should be reverted until proper testing can find and correct this issue.

We generally wouldn't want to do that. Trunk is not stable, and leaving it committed will help us find other issues.

I'm not sure of the timeline of 1.8.6 but I imagine it'll be out soon. I suggest we apply this patch to our 1.8.5 for now. ​http://github.com/jquery/jquery-ui/commit/98a98a05d1a646a1e53b90020fe7c096acd1d933

Replying to nacin:

leaving it committed will help us find other issues.

True.

Replying to nacin:

I suggest we apply this patch to our 1.8.5 for now. ​http://github.com/jquery/jquery-ui/commit/98a98a05d1a646a1e53b90020fe7c096acd1d933

Agreed. I simply don't want a situation where proper widget testing is shelved until jQuery UI 1.8.6 is released.

I played a bit with jQuery UI files updated since v1.8.5 (ui.dialog.js plus another three) but had no luck. Either I am doing something wrong or there is still some issue. This needs to be looked at by one of our JavaScript experts.

Downgrading jQuery UI from v1.8.5 to v1.8.4 fixes the issue for me. I am attaching the downgrade patch for anyone who wants to check.

jQuery UI downgrade from 1.8.5 to 1.8.4

verify-draggability.12863.diff verifies that the item is actually draggable before trying to strip it of its draggability.

(In [15738]) Verify that a widget is draggable before stripping its draggability. props filosofo, see #12863. Fixes widget creation for jQUI 1.8.5; should be fixed in jQUI 1.8.6.