Update to jQuery UI 1.11.2

[Fab1en]

The next version of jQuery UI is out since last august : the ​release post is here. That would be nice to bring it back into core. Change logs : ​1.11.0, ​1.11.1

I'm specifically interested by the following change :

• Fixed: Enabled draggable from within iframe

This would allow to use jQuery UI to drag elements in the customizer preview iframe or in a TinyMCE view iframe.

[wonderboymusic]

@helen or @ocean90 - whoever knows how to update this, someone please grab this

[georgestephanis]

And a recurring friendly reminder to merge #26843 as well once this lands.

[Fab1en]

new files for jQuery UI 1.11.1

[Fab1en]

29833.patch​ drops new files in. I downloaded the files from ​the official github repo, and minify them using Grunt uglify task.

I changed the names from wp-includes/js/jquery/ui/jquery.ui.*.min.js to wp-includes/js/jquery/ui/*.min.js because they were renamed like that in the 1.11.1 release.

They say that

This makes usage with AMD easier (see below) and makes it easier to deal with the individual source files.

I also changed dependencies between modules in order to have the minimum dependency list.

[ocean90]

Yeah, so they changed the build process which doesn't provide separated minified files anymore. :(

@Fab1en Can you please create a patch without renaming the files?

Also for the record: 1.11.x drops support for IE 7 and Opera 12. They will leave the workarounds in 1.11.x, but will drop them in 1.12.x.

[Fab1en]

update files to jQuery UI 1.11.1 without renaming them

[Fab1en]

@ocean90 : I updated the patch.

[ocean90]

Thanks Fabien.

So we now have 3 options:

1) Use jQuery UI without AMD definitions
2) Don't rename current files and update AMD definitions
3) Rename current files, and use the files as they are

Beside this, now and in future we have to the fetch the files from the GitHub repo and minify them by ourselves. Another idea would be to bundle the sources and update our grunt task.

[Fab1en]

I vote for option 3 (so version 1 of my 29833.patch​): I cannot think about any drawbacks to rename the files.
Other options involve complex files manipulations (remove or update part of the source code) without evident benefits.

I also vote for bundling the sources (and the source for jquery as well) as this allows easier js debug. I can propose a new patch for this solution if you want. Or is it a new task (new ticket) ?

[ocean90]

Don't ship non-minified jUI files

[ocean90]

In 29847:

Update jQuery UI to 1.11.1.

Because jQUI's build process no longer provides individual minified files we need some additional changes:

• Rename all files, remove the "jquery.ui." prefix. Add old files to $_old_files.
• Add and use non-minified files in /src.
• Add grunt task to minify jQuery UI files.
• (Non-minified files will not be shipped.)

Changelogs:

• ​http://jqueryui.com/changelog/1.11.0/
• ​http://jqueryui.com/changelog/1.11.1/

props Fab1en, ocean90.
fixes #29833.

[azaozz]

We've always included the "official" builds of external libraries. Not particularly happy that we have to rebuild jQuery UI and bypass the official build on every update. This method is closest to our current setup but might introduce problems if/when the upstream build process changes. Even using different versions of the build tools might be problematic at some point.

It may be possible to split the official build in four parts/files: UI Core, Interactions, Widgets, Effects. The same way as the ​sections on the download page. However not sure this will be better.

As we will be rebuilding UI, we loose the "real life" testing of the builds (i.e. in production we will be running a slightly different code than everybody else). In that terms it is imperative that we adapt and implement the UI's automated tests: ​https://github.com/jquery/jquery-ui/tree/master/tests/unit.

[ocean90]

Replying to azaozz:

We've always included the "official" builds of external libraries. Not happy at all that we have to rebuild jQuery UI and bypass the official build on every update.

That's right. I wasn't happy about it too. But as mentioned above and in linked IRC chat with Scott there will be no official build for individual files anymore.

It may be possible to split the official build in four parts/files: UI Core, Interactions, Widgets, Effects.

Sure, but that means we would blow up our scripts. For example on Dashboard we only need 4 files, when we split it up we would have 9 files in 2 files.

As we will be rebuilding UI, we loose the "real life" testing of the builds (i.e. in production we will be running a slightly different code than everybody else). In that terms it is imperative that we adapt and implement the UI's automated tests: ​https://github.com/jquery/jquery-ui/tree/master/tests/unit.

I'm fine with adding the unit tests too. Is it the same reason why we have the TinyMCE tests?

[nacin]

The TinyMCE tests are nice especially because we hack the hell out of TinyMCE with plugins and such, and because ContentEditable is such a mess.

Committing UI's tests is going to greatly increase our burden in terms of maintaining those tests, while not actually giving us any real benefit. We use an identical build process as the jQuery project. I signed off on this as did the development lead for jQuery UI.

I'd be down for some way to run jQuery UI's tests on uglify'd jQuery UI, and then automate that, but I'd be weary of doing it if it makes it particularly hard for us to maintain it going forward.

[ocean90]

jQuery UI 1.11.2

[ocean90]

In 29920:

Update jQuery UI to 1.11.2.

Changelog: ​http://jqueryui.com/changelog/1.11.2/

see #29833.

[ocean90]

azaozz, what's you opinion on nacin's comment:12?

[azaozz]

Agree that it's going to be hard to maintain UI's tests, quite harder than updating UI. Will have to do more testing "by hand" on every update :)