wrapped and refactored portions of the default transitionHandler function to allow for sequential or simultaneous transitions. The default sequential transition handler for 1.1 should not change at all. Both types are defined as different transition handlers ($.mobile.transitionHandlers.simultaneous and $.mobile.transitionHandlers.sequential), though their logic is shared internally by both to keep overhead low. As was already the case, custom transitions can define a non-default handler by defining a transition handler named the same as the css transition, and referencing one of the existing handlers (or an entirely new one).
updated slide transition to use the simultaneous handler.
changed default of minScrollBack to 250 - the value still claimed in the docs. This reverts @toddparker's change in commit a6dc847474cd43b10d85744c66bd1d9ccce1632a, as a higher number is needed when reintroducing simultaneous transitions
reused some code, removed a var
moved the fallback transition check out of the handler and into nav.js, where it can properly route to the necessary transition handler before calling it.
added back the "slidefade" transition, which is usually preferable to "slide", except in cases where a page is short enough that  a simultaneous transition sequence won't  jump much (which is needed for a regular slide transition). As part of this addition, the keyframes for slidein and slideout are now in their own files, as they are dependencies for these slide transitions
Added metadata for bundle builder
Fixes height of slider handles’ inner elements, thus correcting the highlight’s border radius.
Fixes minor issue where docs footer wasn’t cleared correctly.
Whitespace
Fixes #3898 - Header/footer mini button styles cleaned up. Footer buttons are no longer subject to the same left/right button logic as headers. Default mini/inline styles can now be overridden by setting either attribute to “false”.
Fixed incorrect metadata
Added filter for the web builder service
wrapped and refactored portions of the default transitionHandler function to allow for sequential or simultaneous transitions. The default sequential transition handler for 1.1 should not change at all. Both types are defined as different transition handlers ($.mobile.transitionHandlers.simultaneous and $.mobile.transitionHandlers.sequential), though their logic is shared internally by both to keep overhead low. As was already the case, custom transitions can define a non-default handler by defining a transition handler named the same as the css transition, and referencing one of the existing handlers (or an entirely new one).
updated slide transition to use the simultaneous handler.
changed default of minScrollBack to 250 - the value still claimed in the docs. This reverts @toddparker's change in commit a6dc847474cd43b10d85744c66bd1d9ccce1632a, as a higher number is needed when reintroducing simultaneous transitions
reused some code, removed a var
moved the fallback transition check out of the handler and into nav.js, where it can properly route to the necessary transition handler before calling it.
added back the "slidefade" transition, which is usually preferable to "slide", except in cases where a page is short enough that  a simultaneous transition sequence won't  jump much (which is needed for a regular slide transition). As part of this addition, the keyframes for slidein and slideout are now in their own files, as they are dependencies for these slide transitions
this addresses an issue with iOS5 and possibly others not properly returning to the desired scroll location after a transition that uses 3D transforms.