… $.support.touch though it is still unsupported. Fixes #4786
Created meta-module jquery.mobile.transitions.js
- jquery.mobile.events.orientationchange.js - jquery.mobile.events.throttledresize.js - jquery.mobile.events.touch.js
Removed touch feature test since it's not used anywhere now
This reverts commit 73a61ff.
Can be used to autogenerate dividers for a listview by setting data-autodividers="alpha" (dividers are unique, uppercased single characters from list items) or data-autodividers="full" (unique full text strings selected from list items) on the ul element of the listview. It's also possible to apply a custom selector to find the elements to be used for divider text, with data-autodividers-selector="...". This relates to #2466, but is a different implementation which will automatically update the list dividers if the list elements change. It also has a fairly thorough test suite and documentation.
Conflicts: css/themes/default/jquery.mobile.css css/themes/valencia/jquery.mobile.css css/themes/valencia/jquery.mobile.theme.css js/index.php js/jquery.mobile.js
…e previous messy merge). Docs page is updated to match the new preferred syntax (no changes in API, however)
…hat need to be addressed
…wsers, for all transitions except "fade". By default, these are all set to fall back to "fade", and they'll fall back to "none" if 3D is unsupported and no fallback is defined. They can be overridden at mobileinit, like any other jQM default.
…using native support for CSS position: fixed, where possible. Non-supporting platforms will fall back to inline positioning, either by gracefully degrading on their own or by opting them out through a blacklist (fixed positioning detection's got issues...). unit tests and api documentation coming next, but for the most part, the API is the same as before.