You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although the redesigns introduced breaking changes, 1.12 & 1.13 maintains a lot of compatibility with the 1.11 API by default. This is accomplished by rebuilding the 1.11 API on top of the 1.12/1.13 API. The default behavior for all 1.12 & 1.13 releases will be to simultaneously use the 1.11 and 1.12/1.13 APIs where possible. If you would like to load just the 1.12/1.13 API without the 1.11 API to prepare for jQuery UI 1.14, you can set the $.uiBackCompat flag to false.
Today, jQuery UI announced version 1.13 — its first release in 5 years and the project’s final planned release. [...] 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.
These quotes are contradictory about whether a 1.14 version of jQuery UI is planned.
The text was updated successfully, but these errors were encountered:
I think we will release 1.14. This won't be a big release as previous updates were; we'll just focus on whatever is needed to reduce maintenance burden - dropping some browsers & legacy patches, perhaps turning the $.uiBackCompat flag to false by default, reducing support for compatible jQuery Core releases.
The Reminder: API Redesigns section of the jQuery UI 1.13 Upgrade Guide contains:
Yet, the jQuery maintainers update and transition jQuery UI as part of overall modernization efforts blog post contains:
These quotes are contradictory about whether a 1.14 version of jQuery UI is planned.
The text was updated successfully, but these errors were encountered: