jQuery UI 1.13.0 released

Posted on by

After a long break, it is our pleasure to announce the 1.13.0 release. The main focus of this release was improving compatibility with recent jQuery versions so we postponed most breaking changes like removal of deprecated APIs and removal of legacy browser support to a possible future release.

Usage of deprecated jQuery APIs have been removed. jQuery UI 1.13 triggers no jQuery Migrate warnings when running its test suite against jQuery 3.6.0 with jQuery Migrate 3.3.2, i.e. the latest versions at the moment of this release.

A few security issues have been fixed:

Support for jQuery 1.7 has been dropped; jQuery 1.8 & newer remain supported.

In this release, all individual module files as well as bundled jQuery UI copies produced by the Download Builder have all its code running in strict mode. This shouldn’t matter for most users as jQuery has been running in strict mode since 3.0 released in 2016.

Apart from that, two small features were added:

  1. Accordion’s header option may now accept not only a selector matching header elements but also a function taking the accordion element as a parameter and returning the header elements; more details in the docs for the header option.
  2. Datepicker options now include the optional onUpdateDatepicker callback, called when the datepicker widget’s DOM is updated.

To simplify the maintenance of jQuery UI, we’re sunsetting the old bug tracker at https://bugs.jqueryui.com (we’ll keep it in read-only mode) in favor of GitHub issues.

jQuery UI has struggled with finding contributors for the past few years; our goal is to move it more to a maintenance state: we’ll make sure the library is compatible with new jQuery releases and that security issues are fixed but no new significant feature work is planned. We’ll also try to fix important regressions from jQuery UI 1.12.1; older long-standing bugs may not get fixed. We’ll get a longer blog post about the state of jQuery UI when we release 1.13 final. Note that this does not affect jQuery Core which is still actively maintained.

Download

File Downloads

Git (contains source files, with @VERSION replaced with 1.13.0, base theme only)

Install via bower

  • bower install jquery/jquery-ui#1.13.0

jQuery CDN, powered by StackPath

Google Ajax Libraries API (CDN)

Microsoft Ajax CDN (CDN)

Custom Download Builder

Changelog

See the 1.13 Upgrade Guide for a list of changes that may affect you when upgrading from 1.12.x. For full details on what’s included in this release see the 1.13.0 Changelog.

Thanks

Thanks to all who helped with this release, specifically: A. Wells, Albert Johansson, Alexander Schmitz, c-lambert, claudi, Eirik Sletteberg, Evelyn Masso, Fatér Zsolt, Felix Nagel, Florian Wegscheider, Gez Quinn, GitHub, Horus68, Hrvoje Novosel, Jeremy Mickelson, jigar gala, Jo Liss, Jérémy Munsch, Jörn Zaefferer, Kevin Cupp, Konstantin Dinev, Kyle Rosenberg, Luke Brookhart, Maksymenkov Eugene, Micah Miller, Michał Gołębiowski-Owczarek, Mikolaj Wolicki, milk54, OskarNS, pallxk, Patrick McKay, Paul Capron, Petri Partio, Robert Brignull, Robin, Ryan Oriecuia, sakshi87, Scott González, Sergei Ratnikov, Simon Asika, Szabolcs Szabolcsi-Toth.

Comments

Note: please report bugs to the jQuery UI Bug Tracker; support questions should be posted on Stack Overflow with the jquery-ui tag. Please don’t use comments to report bugs.

If you have feedback on us doing our release for jQuery UI 1.13.0, feel free to leave a comment below. Thank you.

6 thoughts on “jQuery UI 1.13.0 released

  1. jQuery is one of the best supported plugin I have ever used. Thank you everyone involved for the frequent updates and development.

  2. Michał Gołębiowski-Owczarek on said:

    yves: we sent the CDN bundle to Google & Microsoft but we don’t control when they upload the files. The links should start working as soon as they do; before that, you can use the jQuery CDN.

  3. “A few security issues have been fixed.”

    These aren’t marked in the changelog. Is there a list of the specific issues that were fixed anywhere? Are CVEs being obtained for these issues?

  4. Michał Gołębiowski-Owczarek on said:

    David: I just published 3 advisories & I mentioned them in this blog post. I also requested CVEs for them.

Leave a Reply

Your email address will not be published. Required fields are marked *