|
28 | 28 |
|
29 | 29 | <p>Fullscreen fixed toolbars sit on top of the content at all times when they are visible, and unlike regular fixed toolbars, fullscreen toolbars do not fall back to static positioning when toggled. Instead they disappear from the screen entirely. Fullscreen toolbars are ideal for more immersive interfaces, like a photo viewer that is meant to fill the entire screen with the photo itself and no distractions.</p> |
30 | 30 |
|
31 | | - <p>To enable this option on a fixed header or footer, add the <code>data-fullscreen</code> attribute to the element.</p> |
| 31 | + <p>To enable this option on a fixed header or footer, add the <code>data-fullscreen</code> attribute to the element.</p> |
32 | 32 |
|
33 | | - <pre><code> |
| 33 | + <pre><code> |
34 | 34 | <div data-role="header" data-position="fixed" data-fullscreen="true"> |
35 | 35 | <h1>Fixed Header!</h1> |
36 | 36 | </div> |
37 | | - </code></pre> |
| 37 | + </code></pre> |
38 | 38 | <iframe src="/resources/fixedtoolbar/example2.html" style="width:100%;height:420px;border:0px"></iframe> |
39 | 39 |
|
40 | 40 | <h3>Forms in toolbars</h3> |
|
49 | 49 | <p>The fixed toolbar plugin degrades gracefully in platforms that do not support CSS <code>position:fixed</code> properly, such as iOS4.3. If you still need to support fixed toolbars on that platform (with the show/hide behavior) included in previous releases, Filament Group has developed a polyfill that you can use.</p> |
50 | 50 |
|
51 | 51 | <ul> |
52 | | - <li><a href="https://github.com/filamentgroup/jQuery-Mobile-FixedToolbar-Legacy-Polyfill">Github code repository with CSS, and JavaScript required for the fixed toolbars polyfill</a></li> |
53 | | - <li><a href="http://filamentgroup.github.com/jQuery-Mobile-FixedToolbar-Legacy-Polyfill/">Preview URL using the code in the repo above</a></li> |
| 52 | + <li><a href="https://github.com/filamentgroup/jQuery-Mobile-FixedToolbar-Legacy-Polyfill">Github code repository with CSS, and JavaScript required for the fixed toolbars polyfill</a></li> |
| 53 | + <li><a href="http://filamentgroup.github.com/jQuery-Mobile-FixedToolbar-Legacy-Polyfill/">Preview URL using the code in the repo above</a></li> |
54 | 54 | </ul> |
55 | 55 |
|
56 | 56 | <p>Just include the CSS and JS files after your references to jQuery Mobile and Fixed toolbars will work similarly to jQuery Mobile 1.0 in iOS4.3, with the inclusion of the new API for the 1.1 fixedtoolbar plugin.</p> |
|
59 | 59 |
|
60 | 60 | <h3>Known issue with form controls inside fixed toolbars, and programmatic scroll</h3> |
61 | 61 | <p>An obscure issue exists in iOS5 and some Android platforms where form controls placed inside fixed-positioned containers can lose their hit area when the window is programatically scrolled (using <code>window.scrollTo</code> for example). This is not an issue specific to jQuery Mobile, but because of it, we recommend not programatically scrolling a document when using form controls inside jQuery Mobile fixed toolbars. <a href="https://github.com/scottjehl/Device-Bugs/issues/1">This ticket</a> from the <a href="https://github.com/scottjehl/Device-Bugs/">Device Bugs project</a> tracker explains this problem in more detail.</p> |
62 | | - |
63 | | - |
| 62 | + |
64 | 63 | <h3>Known issues in Android 2.2/2.3</h3> |
65 | 64 | <p>Android 2.2/2.3's implementation of <code>position: fixed;</code> can, in conjunction with seemingly unrelated styles and markup patterns, cause a number of strange issues, particularly in the case of <code>position: absolute</code> elements inside of <code>position: fixed</code> elements. While we've done our best to work around a number of these unique bugs within the scope of the library, custom styles may cause a number of issues.</p> |
66 | 65 | <ul> |
|
73 | 72 |
|
74 | 73 | <p>While we will continue to try to find ways to mitigate these bugs as best we can, we currently advise against implementing fixed toolbars containing complicated user styles and form elements without extensive testing in all versions of Android's native browser.</p> |
75 | 74 |
|
76 | | - |
77 | | -<div class="ui-body ui-body-e"> |
78 | | - <h2>No longer supported: touchOverflowEnabled</h2> |
79 | | - |
80 | | - <p>Prior to jQuery Mobile 1.1, true fixed toolbar support was contingent on native browser support for the CSS property <code>overflow-scrolling: touch</code>, which is currently only supported in iOS5. As of version 1.1, jQuery Mobile no longer uses this CSS property at all. We've removed all internal usage of this property in the framework, but we've left it defined globally on the $.mobile object to reduce the risk that its removal will cause trouble with existing applications. This property is flagged for removal, so please update your code to no longer use it. The support test for this property, however, remains defined under <code>$.support</code> and we have no plans to remove that test at this time. </p> |
81 | | -</div> |
| 75 | + <div class="warning"> |
| 76 | + <h2>No longer supported: touchOverflowEnabled</h2> |
| 77 | + <p>Prior to jQuery Mobile 1.1, true fixed toolbar support was contingent on native browser support for the CSS property <code>overflow-scrolling: touch</code>, which is currently only supported in iOS5. As of version 1.1, jQuery Mobile no longer uses this CSS property at all. We've removed all internal usage of this property in the framework, but we've left it defined globally on the $.mobile object to reduce the risk that its removal will cause trouble with existing applications. This property is flagged for removal, so please update your code to no longer use it. The support test for this property, however, remains defined under <code>$.support</code> and we have no plans to remove that test at this time. </p> |
| 78 | + </div> |
82 | 79 |
|
83 | 80 | </longdesc> |
84 | 81 | <added>1.0</added> |
@@ -195,24 +192,26 @@ $( document ).on( "mobileinit", function() { |
195 | 192 | </methods> |
196 | 193 | <example> |
197 | 194 | <desc>A basic example of a page with fixed toolbars.</desc> |
198 | | - <html><![CDATA[<div data-role="header" <div data-role="header" data-position="fixed" data-theme="a"> |
| 195 | + <html><![CDATA[ |
| 196 | +<div data-role="page" id="page1"> |
| 197 | + <div data-role="header" data-position="fixed" data-theme="a"> |
199 | 198 | <h1>Fixed Header</h1> |
200 | 199 | </div> |
201 | 200 | <div data-role="content" > |
202 | | - |
203 | 201 | <p>This page demonstrates the "fixed" toolbar mode. </p> |
204 | 202 | <br /><br /> |
205 | 203 | <p>To enable this toolbar feature type, you apply the <code>data-position="fixed"</code> attribute to both the header and footer <code>div</code> elements.</p> |
206 | 204 | <br /><br /> |
207 | 205 | <p>And we're adding more text here so that you can really see the fixed toobars in action.</p> |
208 | 206 | <br /><br /> |
209 | 207 | <p>If you tap the screen while in the middle of the page (i.e. neither at the top nor the bottom of the page, the visibility of the toolbars will toggle</p> |
210 | | - <p></p> |
211 | | - |
| 208 | + <p></p> |
212 | 209 | </div> |
213 | 210 | <div data-role="footer" data-theme="a" data-position="fixed"> |
214 | 211 | <h1>Fixed Footer</h1> |
215 | | - </div>]]></html> |
| 212 | + </div> |
| 213 | +</div> |
| 214 | +]]></html> |
216 | 215 | </example> |
217 | 216 | <category slug="widgets"/> |
218 | 217 | </entry> |
0 commit comments