![]() Therefore, the number of breaking changes is extremely limited compared to previous upgrades. Removal of deprecated APIs and removal of legacy browser support are not included. The main focus of this release was improving compatibility with recent jQuery versions. Even though the 1.11 API is deprecated, it's important for 1.13 releases not to regress so that users are encouraged to upgrade even if they're not ready to use the new APIs. If you find a regression from the 1.11 API, please report it in the bug tracker. 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. 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. ![]() This is accomplished by rebuilding the 1.11 API on top of the 1.12/1.13 API. Although the redesigns introduced breaking changes, 1.12 & 1.13 maintains a lot of compatibility with the 1.11 API by default. You can read about the API redesign process on the JQuery UI 1.12 introduced API redesigns for Button, Buttonset, Dialog, Draggable, Droppable, Menu, Mouse, Resizable, Selectable, Sortable, Tabs, Tooltip, and Effects. ![]() All changes are listed below, organized by plugin, along with how to upgrade your code to work with jQuery UI 1.13. This guide will assist in upgrading from jQuery UI 1.12.x to jQuery UI 1.13.x. Various *Text options no longer accept HTML input.Added function value for a header option.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |