Date: Fri, 10 May 2024 16:20:15 +0200
Subject: [PATCH] All: Upgrade the docs for latest UI 1.13 & upcoming 1.14
changes
Changes:
1. Properly reflect testing against newer jQuery Core on the home page.
2. Update 1.12 & 1.13 upgrade guides to no longer claim 1.11 compatibility
will be completely dropped in 1.14. Mention a future jQuery UI release
instead as we don't want to commit to a specific version at this point.
---
page/index.html | 9 ++++++---
page/upgrade-guide/1.12.md | 4 ++--
page/upgrade-guide/1.13.md | 2 +-
3 files changed, 9 insertions(+), 6 deletions(-)
diff --git a/page/index.html b/page/index.html
index 233746f..9764fd4 100644
--- a/page/index.html
+++ b/page/index.html
@@ -67,11 +67,14 @@ Developer Links
What's New in jQuery UI 1.13?
-Compatibility with recent jQuery versions (up to 3.6): 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 its release.
+Compatibility with recent jQuery versions (up to 3.7): Usage of deprecated jQuery APIs have been removed. jQuery UI 1.13.3 triggers no jQuery Migrate warnings when running its test suite against jQuery 3.7.1 with jQuery Migrate 3.4.1, i.e. the latest versions at the moment of its release.
Interested in the full details of what changed? Check out the
-1.13 upgrade guide, and
-1.13.0 changelog.
+1.13 upgrade guide,
+1.13.0 changelog,
+1.13.1 changelog,
+1.13.2 changelog, and
+1.13.3 changelog.
Dive In!
diff --git a/page/upgrade-guide/1.12.md b/page/upgrade-guide/1.12.md
index 4c49eb7..5790d57 100644
--- a/page/upgrade-guide/1.12.md
+++ b/page/upgrade-guide/1.12.md
@@ -18,9 +18,9 @@ jQuery UI 1.12 introduces API redesigns for Button, Buttonset, Dialog, Draggable
```
-### Preparing for jQuery UI 1.14
+### Preparing for a future jQuery UI release
-The API redesigns deprecate some functionality, which will be removed in 1.14. You don't have to wait for the 1.14.0 release in order to find out if your code will work when the 1.11 APIs are removed. You can use the `$.uiBackCompat` flag to test this with any 1.12 release.
+The API redesigns deprecate some functionality, which will be removed in the future. You don't have to wait in order to find out if your code will work when the 1.11 APIs are removed. You can use the `$.uiBackCompat` flag to test this with any 1.12 release.
If you find a regression from the 1.11 API, please report it in the bug tracker. Even though the 1.11 API is deprecated, it's important for 1.12 releases not to regress so that users are encouraged to upgrade even if they're not ready to use the new APIs. Note that
most 1.10 APIs which were deprecated in 1.11 were removed in 1.12 and will not exist, regardless of the $.uiBackCompat flag.
diff --git a/page/upgrade-guide/1.13.md b/page/upgrade-guide/1.13.md
index 86fd7d9..7a1657e 100644
--- a/page/upgrade-guide/1.13.md
+++ b/page/upgrade-guide/1.13.md
@@ -10,7 +10,7 @@ This guide will assist in upgrading from jQuery UI 1.12.x to jQuery UI 1.13.x. A
## Reminder: API Redesigns
jQuery UI 1.12 introduced API redesigns for Button, Buttonset, Dialog, Draggable, Droppable, Menu, Mouse, Resizable, Selectable, Sortable, Tabs, Tooltip, and Effects. You can read about the API redesign process on the
-[jQuery UI Blog](https://blog.jqueryui.com/2011/03/api-redesigns-the-past-present-and-future/). 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`.
+[jQuery UI Blog](https://blog.jqueryui.com/2011/03/api-redesigns-the-past-present-and-future/). 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 removal of these legacy APIs, you can set the `$.uiBackCompat` flag to `false`.
```html