After a long break, it is our pleasure to announce the 1.13.0-rc.2 release. The release is feature-complete, we just wanted to give developers some time to test it & report any critical issues before we release the final. We didn’t find any such issues during our internal testing. If no blocking issues get reported, we expect to release 1.13.0 final in a few weeks.
You might be wondering what happened to 1.13.0-rc.1. A critical issue in the release script made the final built file not work at all, only individual AMD modules were fine. This made us not announce that 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.
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:
- 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.
- 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.
Git (contains source files, with @VERSION not yet replaced with 1.13.0-rc.2, base theme only)
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 RC release for jQuery UI 1.13.0, feel free to leave a comment below. Thank you.