Skip to content
This repository has been archived by the owner on Oct 8, 2021. It is now read-only.

1.3 Release Notes

Jump to bottom
toddparker edited this page Dec 6, 2012 · 44 revisions

Key Changes

Upgrade notes

Rounded corner class changes - In 1.3, we've changed the way rounded corners are applied across all widgets. In previous versions, we had fairly complex JS logic to dynamically apply corner classes to specific elements in a widget. For example, the first item in an inset listview would get the ui-corners-top class to round only the top left and right corners and a similar thing would happen for bottom corners. // Explain how the new JS works.

Theme CSS corner classes

Icons

Controlgroup

Listview

Popup

Textinput

Select

RWD tables

Dialog

  • New option: closeBtn (or data-close-btn in the DOM) has three values: "left", "right", and "none". See https://github.com/jquery/jquery-mobile/issues/3886. "left" means a close button will be added to the left edge of the header. "right" means such a button will be added to the right edge of the header. "none" means no button will be added. This latter option allows for the manual addition of buttons to the header which can act as custom close buttons (see https://github.com/jquery/jquery-mobile/issues/5117).
  • New option "corners" (no issue ticket, landed with CSS corner styling)

Navigate event and method

There are two new additions to the navigation functionality in jQuery Mobile. A navigate event that normalizes the URL alteration events hashchange/popstate, and a $.navigate method that allows users to receive extended traversal information in navigate bindings (eg, directionality).

The navigate event is a light weight attempt to unify bindings to a browser's URL alteration events hashchange and popstate. It also handles differences in the way setting the hash on the location object interacts with the two browser events (ie, stop the world popstate triggering) , and provides event hooks to control the event lifecycle.

The $.navigate method forms the bulk of the new functionality. By using the $.navigate method to do url manipulation instead of doing it directly with the location object, replaceState, or pushState you get history management and support for both modes of URL state tracking. The history management provides a state object to navigate event bindings whether the browser supports the new history API or not. In addition it contains the same logic used in jQuery Mobile to determine what direction the browser history is moving.

Both the event and the method are available as modules apart from other navigation functionality in jQuery Mobile, with minor dependencies on other parts of the library. More info: https://github.com/jquery/jquery-mobile/issues/5091

Fixed Toolbars

Button

Collapsibles

  • New option "corners" for inset collapsibles and collapsible set (no issue ticket, landed with CSS corner styling)

Fieldcontain

Transitions

Clone this wiki locally