@@ -132,6 +132,12 @@ <h2>Defining fallback transitions for non-3D support</h2>
<p>The fallback transition for browsers that don't support 3D transforms can be configured for each transition type, but by default we specify "fade" as the fallback. For example, this will set the fallback transition for the slideout transition to "none":</p>
+ <p>By default, transitions are disabled (set to "none") when you’re either coming FROM or going TO a page where the scroll position is 3x the height of the device’s screen.
+ This feature was added because of the slow response times and the possibility of browser crashing when clicking on a list item (or any navigation element) far down a long page which leads to the
+ browser trying to animate a really massively tall page from the scroll position to the top of the screen. The scroll position, not total screen height, is the determining factor for performance.
+ This scroll position breakpoint is configurable via the new <code>getMaxScrollForTransition</code> function.</p>
+
<h2>Setting a max width for transitions</h2>
<p>By default, transitions can be disabled (set to "none") when the window width is greater than a certain pixel width. This feature is useful because transitions can be distracting or perform poorly on larger screens. This value is configurable via the global option <code>$.mobile.maxTransitionWidth</code>, which defaults to <code>false</code>. The option accepts any number representing a pixel width or <code>false</code> value. If it's not <code>false</code>, the handler will use a "none" transition when the window width is wider than the specified value.</p>
0 comments on commit
6c9b169