jQuery UI 1.14.0 released

Posted on by

We are happy to announce the 1.14.0 stable release! The focus of this release is reducing the maintenance burden to ensure important issues are addressed, as outlined in the blog post about plans for jQuery UI 1.14. As of today, the jQuery UI 1.13.x line is no longer supported.

Reduced support for older browsers or jQuery

jQuery UI 1.14 finally drops support for all versions of Internet Explorer & Edge Legacy. Only the latest version of Chrome, Firefox, Safari & Edge are officially supported. Contrary to what we did in past releases, code supporting unsupported browsers has been deleted.

Support for jQuery 1.7-1.11, 2.0-2.1 & 3.0-3.5 has been dropped.

This release has been tested against jQuery 1.12.4, 2.2.4, 3.6.4 & 3.7.1. Since jQuery follows semver, newer jQuery <4 versions within each major version line should generally work as well.

jQuery UI 1.14 triggers no jQuery Migrate warnings when running its test suite against jQuery 3.7.1 with jQuery Migrate 3.5.2, i.e. the latest versions at the time of this release.

Breaking changes

Backward compatibility with the 1.11 API is disabled by default. To enable it (restoring the default 1.13 behavior), set the jQuery.uiBackCompat flag to true. We encourage trying without the compatibility layer, though – maybe your app is already using new APIs exclusively? If there are any feature gaps from the old APIs, please submit issues.

A few APIs have been removed as they were no longer needed after dropping IE support: $.fn._form, $.ui.ie, $.ui.safeActiveElement & $.ui.safeBlur. See the 1.14 Upgrade Guide for information about replacements.

The Download Builder now only supports jQuery UI 1.12 & newer. This change happened independently from the jQuery UI 1.14 release, but it’s worth reminding.

Feature: aria-modal support in the dialog widget

Modal dialogs now get the aria-modal=”true” attribute added. Thanks to that, modal dialogs cause the elements outside of the dialog to be excluded from the accessibility tree, making some accessibility tools more useful. See issue #2246 for more information.

Test infrastructure changes

jQuery UI 1.14 is tested in all supported browsers & jQuery Core versions not only post-merge as was done in the past, but also on every pull request via GitHub Actions. That should make contributing to jQuery UI easier.

This improvement was made possible by a major rewrite of jQuery UI test infrastructure, which removed all deprecated or under-supported dependencies.

Reminder about maintenance state

Please remember jQuery UI is in 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. Note that this does not affect jQuery Core which is in active development.

Download

File Downloads

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

Install via bower

  • bower install jquery/jquery-ui#1.14.0

jQuery CDN

Google Ajax Libraries API (CDN)

Microsoft Ajax CDN (CDN)

Custom Download Builder

Changelog

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

Thanks

Thanks to all who helped with this release, specifically: Michał Gołębiowski-Owczarek, Porter Clevidence, Ralf Koller, Timmy Willison, and Felix Nagel.

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.14.0, feel free to leave a comment below. Thank you.

jQuery UI 1.14.0-beta.2 released

Posted on by

Following up on our blog post on Plans for jQuery UI 1.14, it is our pleasure to announce the second beta for jQuery UI 1.14.0.

Compared to the first beta, there are two main changes:

  • Support for aria-modal attribute in dialogs have been added (PR #2257).
  • The release is now fully supported in the jQuery UI Download Builder; zip files are also available.

We’ve also finalized the migration from the TestSwarm test runner to our custom one integrated into GitHub Actions.

See the jQuery UI 1.14.0-beta.1 blog post for information about changes already available in the first beta.

Please remember jQuery UI is in 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. 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.14.0-beta.2, base theme only)

Install via npm

  • npm install jquery-ui@1.14.0-beta.2

Install via bower

  • bower install jquery/jquery-ui#1.14.0-beta.2

jQuery CDN

Changelog

For full details on what’s included in this release see the 1.14.0-beta.2 Changelog. The 1.14 Upgrade Guide will be available later.

Thanks

Thanks to all who helped with this release, specifically: Ralf Koller, Michał Gołębiowski-Owczarek, Timmy Willison.

Comments

Note: Please report bugs to the jQuery UI Bug Tracker. Support questions should be posted on Stack Overflow with the jquery-ui tag.

jQuery UI 1.14.0-beta.1 released

Posted on by

Following up on our blog post on Plans for jQuery UI 1.14, it is our pleasure to announce the first beta for jQuery UI 1.14.0.

This release doesn’t offer any new features, only the following breaking changes:

  • Only the latest version of Chrome, Firefox, Safari & Edge are officially supported; there is no support for any version of IE and Edge Legacy. Contrary to what was done in past releases, code supporting unsupported browsers has been deleted.
  • Only the latest jQuery version within each major version of jQuery Core is supported. This beta was tested against jQuery 1.12.4, 2.2.4 & 3.7.1, plus two development versions: 3.x & 4.x.
  • Backwards compatibility with the 1.11 API is disabled by default. To re-enable it (restoring the default 1.13 behavior) set the jQuery.uiBackCompat flag to true.

This beta is not integrated into the jQuery UI Download Builder; support for jQuery UI 1.14 will be added before the final release. Because of that, zip bundles are not available for this beta.

We’d also like to remind you that beginning in June 2024, the Download Builder will only support jQuery UI 1.12 or newer. For more information, please read the Plans for jQuery UI 1.14 blog post.

Please remember jQuery UI is in 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. Note that this does not affect jQuery Core, which is still actively maintained.

Download

Git (contains source files, with @VERSION replaced with 1.14.0-beta.1, base theme only)

Install via npm

  • npm install jquery-ui@1.14.0-beta.1

Install via bower

  • bower install jquery/jquery-ui#1.14.0-beta.1

jQuery CDN

Changelog

For full details on what’s included in this release see the 1.14.0-beta.1 Changelog. The 1.14 Upgrade Guide will be available later.

Thanks

Thanks to all who helped with this release, specifically: Michał Gołębiowski-Owczarek, Timmy Willison, Felix Nagel.

Comments

Note: Please report bugs to the jQuery UI Bug Tracker. Support questions should be posted on Stack Overflow with the jquery-ui tag.

Plans for jQuery UI 1.14, dropping support for UI <1.12 in the Download Builder

Posted on by

jQuery UI has been in maintenance mode since 2021. We are prioritizing security issues & regressions from jQuery UI 1.12, with occasional fixes contributed by the community. That said, maintaining jQuery UI still takes a significant effort. This is caused by many moving pieces:

  • jQuery UI 1.13 supports jQuery 1.8 & newer. This means jQuery UI is currently tested against every major and minor jQuery release since jQuery 1.8, in all supported browsers, and in development versions of jQuery. This amounts to 18 test variants in total.
  • jQuery UI is tested against the latest two versions of Chrome, Firefox, Safari, Opera & Edge, Edge Legacy & IE 11.
  • The Download Builder supports jQuery UI 1.9 & newer – that’s 5 versions, the older of which was first released in 2012. Each of those versions has custom builder code that needs maintenance.
  • Most of the testing is only done post-commit; PRs have had limited testing so far.

The above issues, combined with the fact very few people work on jQuery UI in their limited time, result in delays—1 year and 9 months have passed between the 1.13.2 and 1.13.3 releases. If we want to continue supporting jQuery UI, we need to reduce some of this complexity.

We are planning the following changes to ease the maintenance effort:

  • Beginning in June, 2024, the Download Builder will only support jQuery UI 1.12 or newer. If you rely on built-in themes, you’ll still be able to download full builds of previous releases from the releases page after this date.
  • jQuery UI 1.14 will only be tested on the latest version of Chrome, Firefox, Safari & Edge. It will not support IE and Edge Legacy. Contrary to what was done in past releases, code supporting unsupported browsers will be deleted.
  • Only the latest jQuery version within each major version of jQuery Core will be supported. As of the publication date of this blog post, that would be jQuery 1.12.4, 2.2.4 & 3.7.1, plus two development versions: 3.x & 4.x.
  • All browsers supported by jQuery UI 1.14 will be tested on PRs via the same custom test runner as jQuery Core. This will help catch issues before problematic code gets merged. In fact, this change has already landed!
  • jQuery UI 1.14 will have the jQuery.uiBackCompat flag set to false. We are not planning new big compatibility breaks and this will help people discover accidental reliance on deprecated behaviors.
  • Support for jQuery UI 1.13 will end on the day jQuery UI 1.14.0 is released.

We understand these changes may be disrupting for some teams. However, we need to balance limited resources with still being able to address more important issues. We think the above plan is the best way to achieve this goal.

jQuery UI 1.13.3 released

Posted on by

We’re happy to announce the third patch release to jQuery UI 1.13 is out. It includes fixes for the resizable widget when a global box-sizing: border-box CSS declaration is present (a common complaint was about resizable dialogs), support for the hidden attribute in selectmenu options, fixes for the deprecated -ms-filter syntax, and correcting the format of the deprecated ui/core.js AMD module.

jQuery UI has a new test runner ported from jQuery that allows local & BrowserStack test runs without reliance on Karma. As an added bonus, we’re now running tests against Chrome, Firefox, Safari & Edge against latest jQuery 1.x, 2.x, 3.x & the development version in GitHub CI, allowing to detect more issues at the pull request level. This will also be a basis for a future jQuery UI 1.14 – but that’s a topic for a separate blog post.

Please remember jQuery UI is in 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. 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.3, base theme only)

Install via npm

  • npm install jquery-ui@1.13.3

Install via bower

  • bower install jquery/jquery-ui#1.13.3

jQuery CDN

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.3 Changelog.

Thanks

Thanks to all who helped with this release, specifically: Ashish Kurmi, DeerBear, divdeploy, Kenneth DeBacker, mark van tilburg, Matías Cánepa, Michał Gołębiowski-Owczarek, Timmy Willison, Timo Tijhof, Дилян Палаузов, Felix Nagel.

Comments

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

jQuery UI 1.13.2 released

Posted on by

We’re happy to announce the second patch release to jQuery UI 1.13 is out. It includes a security fix for the Checkboxradio widget, a few localization updates for Datepicker and some fixes for issues submitted by the community. Built jQuery UI files are now included in the npm package; this was important to some CDNs that rely on it as the source of truth.

More details about the security issue fixed:

Please remember jQuery UI is in 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. 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.2, base theme only)

Install via npm

  • npm install jquery-ui@1.13.2

Install via bower

  • bower install jquery/jquery-ui#1.13.2

jQuery CDN

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.2 Changelog.

Thanks

Thanks to all who helped with this release, specifically: Adam Lidén Hällgren, Christian Oliff, Denny Septian Panggabean, Felix Nagel, James Hinderks, Michał Gołębiowski-Owczarek.

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.2, feel free to leave a comment below. Thank you.

jQuery UI 1.13.1 released

Posted on by

We’re happy to announce the first patch release to jQuery UI 1.13 is out. It mostly consists of fixes for 1.13 regressions reported to us since the 1.13.0 release. Fixes involve the Widget, Autocomplete, Sortable & Tooltip modules.

Please remember jQuery UI is in 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. 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.1, base theme only)

Install via bower

  • bower install jquery/jquery-ui#1.13.1

jQuery CDN

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.1 Changelog.

Thanks

Thanks to all who helped with this release, specifically: Ben Mullins, Felix Nagel, GitHub, Josep Sanz, Michał Gołębiowski-Owczarek.

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.1, feel free to leave a comment below. Thank you.

jQuery maintainers continue modernization initiative with deprecation of jQuery Mobile

Posted on by

By: Michał Gołębiowski-Owczarek, Felix Nagel, and the jQuery team

Editor’s Note: the following blog post was originally published to the OpenJS Foundation Blog.

jQuery maintainers are continuing to modernize its overall project that still is one of the most widely deployed JavaScript libraries today. The team announced that the cross-platform jQuery Mobile project under its umbrella will be fully deprecated as of October 7, 2021. New technologies for mobile app development have evolved since this project was launched in 2010, so we’re encouraging developers to plan for this jQuery Mobile transition.

Please note that:

  • The Download Builder will remain available.
  • Mobile 1.4 is not compatible with the latest jQuery Core.
  • Issues will be turned off. Please report critical security bugs via email to security@jquery.com. 

Celebrating jQuery Mobile’s History

jQuery Mobile was conceived and announced in 2010, three years after the launch of jQuery.  The project was exciting and ambitious. At announcement, jQuery Mobile promised compatibility across multiple platforms, browsers, and versions. Several mobile browser vendors, including Palm and Mozilla, signed on to sponsor the project: 


“The jQuery community has focused on making the Web as productive and fun as possible. When we heard the mission behind jQuery Mobile, we wanted to help. With webOS we have shown that the Web platform is fantastic for developers, so we are excited to help make jQuery Mobile as good as it can be.” -Dion Almaer – Palm

At the time, the mobile web was desperately in need of a framework capable of working across all browsers, allowing developers to build truly mobile web applications. jQuery had already changed the way developers were building on the web, making it easier (and faster) to create secure, compliant applications. 

With jQuery Mobile, the project’s goals were to bring the ease-of-use of jQuery to HTML-capable mobile device browsers and to make it easier for developers to build progressively enhanced web applications. Led by Todd Parker of Filament Group, a development studio known for their work on cross platform and accessibility-first applications, jQuery Mobile launched its alpha release in October 2010. 

Alpha features included several components, layouts and theming tools that simplified the process of building a mobile web application. Progressive enhancement and graceful degradation, which were hot (and tricky) topics in web development at the time, featured heavily: jQuery Mobile promised developers and users the best possible experience their platform could handle. Accessibility was another key feature, with Mobile promising a user experience that could be navigated by touch, keyboard, or screen reader via ARIA compatible components. Additional features such as simplicity, file size, and the ability to deploy jQuery Mobile applications through an app store drove further excitement. 

Over the next year, the jQuery Mobile team continued to add compatible platforms and browsers, new components and themes, and eventually a themeroller tool that allowed developers to configure and download themes without writing any CSS. 

The community response was overwhelming – by the time 1.0 was released in November 2011, jQuery Mobile had gathered over 125 contributors, dozens of articles, tutorials and demos, 8 published books, and a gallery of sites, plugins and extensions to welcome and introduce new developers to the project. 

jQuery Mobile continued to make monthly releases throughout 2012 and 2013, regularly adding and improving components, resolving compatibility issues with mobile browsers, and making performance improvements to speed up page rendering times. The development team also continued to prioritize and highlight the importance of responsive web design and accessibility principles with each new release. 

As the number of components and widgets swelled – both those that were officially supported or widely adopted in the community, performance and compatibility issues with mobile platforms, browsers, and jQuery core were also exacerbated. Though the project did have some automated tests, there were still a number of items that needed to be tested manually, which slowed down the development process. 

In mid 2013, Jasper de Groot became the project lead and announced tighter development collaboration between jQuery UI and jQuery Mobile teams, sharing goals, roadmaps and code in order to ease the workload for both groups. The team continued to provide maintenance releases and support, but progress continued to slow under the burden of testing and supporting such a large community. 

Alex Schmitz took over the lead in July 2014, but by that time the size of the project, combined with the pace and availability of new mobile browser features, made finding a viable path forward for the project increasingly difficult. 

The latest stable version was released October 2014. Alex and team made a big push to update jQuery Mobile again in 2017 with the release of an alpha version of 1.5; this version would see compatibility with jQuery 3.0 and npm support among other things.

jQuery Mobile became an OpenJS Foundation Emeritus project in 2018, signifying that the goals of the project had been achieved.

jQuery modernization initiative

The depreciation of jQuery mobile follows the careful transition of another project under the jQuery project umbrella, jQuery UI.

jQuery Core is still actively maintained and widely implemented. As part of its modernization initiative, the team also has been making a series of updates this year to its infrastructure, including migrating and improving its CDN.

Celebrating jQuery Mobile Maintainers and Contributors

The contributions to jQuery Mobile opened up opportunities for people and organizations around the world, and we are thankful for all the contributions over the years. We would like to give an extra shout out of gratitude to the past maintainers of jQuery Mobile: Alexander Schmitz, Jasper de Groot, and Todd Parker.

jQuery maintainers update and transition jQuery UI as part of overall modernization efforts

Posted on by

By: Michał Gołębiowski-Owczarek, Felix Nagel, and the jQuery team

Editor’s Note: the following blog post was originally published to the OpenJS Foundation Blog.

The jQuery project is actively maintained and widely implemented — it’s used by 73% of 10 million most popular websites. As part of its ongoing effort to modernize the project, jQuery maintainers have taken steps to wind down one of its projects under the jQuery umbrella through a careful transition. 

Today, jQuery UI announced version 1.13 — its first release in 5 years and the project’s final planned release[1]. Perhaps the most important update is that jQuery UI 1.13 now runs on the latest version of jQuery Core, providing a number of browser compatibility and security updates that have been missing from previous releases, in addition to community fixes and improvements. The jQuery UI Download Builder has also been restored and updated so developers can continue to download UI along with their favorite themes. The release is part of an ongoing series of updates across all jQuery projects.

jQuery UI is in maintenance-only mode. Users should not expect any new releases, though patches may be issued to resolve critical security, interoperability, or regression bugs. Trac, the project’s bug-tracking tool, has been put in read-only mode and developers are asked to file any critical issues on the project’s GitHub repository

jQuery UI was first launched in September 2007 as a curated set of user interface interactions, effects, widgets, and themes built on top of the jQuery library. It quickly gained popularity because it was one of the best tested and most accessible UI frameworks of its time. The tool helped developers build UI components such as form controls and date pickers using the best practices back then. In its heyday, jQuery UI was adopted by a broad set of enterprises including Pinterest, PayPal, IMDB, Huffington Post, and Netflix. 

Today, jQuery UI continues to be an important testbed for jQuery Core updates, helping the maintainer team spot bugs and interoperability issues that arise as the web platform evolves. 

Celebrating jQuery UI’s History

With the launch of jQuery in 2006, web developers were able to access and manipulate DOM and CSS faster and easier than ever before. Thousands of open source jQuery widgets and plugins were created to handle previously tricky problems, like showing and hiding elements, rotating through image carousels, or picking dates on a calendar. The jQuery ecosystem became a playground full of tools for making new and interesting interactions possible on the web. 

‘New and interesting’ doesn’t always translate to ‘good and useful’ — though there were many good plugins available, it was not always easy to tell which would be the most performant or provide the best user experience. Developers might have to go searching for the right tools or worse, spend significant time swapping through several plugins to figure out which one worked best. Further, there were few examples of best practices in user experience on the web, so visitors to one website could have vastly different (and thus confusing) interactions when they performed a similar task on another website. 

Members of the jQuery Core team wanted to help developers write performant, high-quality, and reusable jQuery components for their sites and applications. After some discussion, the idea for a second library with strict standards for coding, documentation, and theming was born. The project’s vision and goals included: developing a collaborative design process; providing flexible styling and themes; creating elegant visual and interaction design; providing a robust API; and prioritizing progressive enhancement, accessibility, internationalization and localization support.

In September 2007, jQuery UI officially launched as a set of user interface interactions, effects, widgets, and themes built on top of jQuery. Soon after, the team shifted their focus to provide a full set of APIs and methods to allow developers to create flexible, full-featured widgets that met high standards of quality. CSS effects such as easing and animation were added in and helped developers create more modern, enhanced experiences. The team at Filament Group later added a ThemeRoller, allowing developers to get started quickly by providing customizable theme boilerplate. ThemeRoller is still operational today.  

By the end of 2008, jQuery UI had an exploding community of users, developers, and interaction designers regularly providing updates and improvements to the project as best practices and style preferences evolved. Between 2009 and 2016, the community provided a variety of new official and unofficial themes and plugins, interoperability and other bug fixes, robust testing processes, and support for multiple versions of jQuery. 

jQuery UI’s prior official release came in September 2016, nearly a decade after it started. In that timeframe, the jQuery community had helped inspire dozens of other open source projects, pattern and component libraries. But newer CSS frameworks and approaches were taking hold, and slowly the community moved on to other projects. The UI team and jQuery Mobile teams merged, and the group focused more on maintenance and compatibility with jQuery Core.  

jQuery UI became an OpenJS Foundation Emeritus project in 2018, recognizing that it was winding down while noting the significance it had for the JavaScript ecosystem.

Celebrating jQuery UI Maintainers and Contributors

The scope of the project and the inclusiveness of the community was responsible for helping countless web makers develop a love and appreciation for user experience, localization, internationalization, accessibility, and clean, reusable code. Though many hours of work and contribution went into making jQuery UI a successful library, the jQuery UI core team deserves extra recognition for more than a decade of hard work shepherding the work and the community throughout the project’s lifecycle. Alex Schmitz, Jörn Zaefferer, Felix Nagel, Mike Sherov, Rafael Xavier de Souza, and Scott González led a team of many core contributors and more than 300 additional authors.

Additional gratitude is owed to Michał Gołębiowski-Owczarek for preparing the 1.13 release and stewarding the repository for the past year. 

OpenJS Foundation will forever be grateful for the work of these open source developers and the impact they had on the ecosystem through their work. Please join us in celebrating these developers and jQuery UI!

References

1. jQuery UI 1.13 will not be the final release in the end, see the new plans in the blog post Plans for jQuery UI 1.14, dropping support for UI <1.12 in the Download Builder.

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

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.