Commit graph

13 commits

Author SHA1 Message Date
scottjehl
a75f4d1361 removed debug line 2011-12-27 21:07:50 +07:00
scottjehl
a89f2989eb blacklisted Opera Mobile from fixies 2011-12-27 20:51:29 +07:00
scottjehl
273642e2bc cleaned up the opt-out formatting and added Fennec < 6 and WebOS < 3. 2011-12-26 21:29:29 +07:00
scottjehl
ca3f67981e Blocked out Android 2.1 and older, running Webkit version older than 233 (the one that comes with 2.2) 2011-12-26 19:30:09 +07:00
scottjehl
5de358b8a5 make sure all page classes are removed at destroy 2011-12-20 17:45:38 +07:00
scottjehl
aae2d1b22c ensure tapping the toolbar itself (or something in it) will not trigger a toggle of the toolbars. 2011-12-20 17:44:20 +07:00
scottjehl
d442a0bc0f removed commented-out code for polyfilling fixed support - it wouldn't have worked as we'd want it to anyway. 2011-12-20 17:38:05 +07:00
scottjehl
6bc63b7f09 fixed the page class name for fullscreen to include "header" or "footer". Also improved the show and hide methods so that they don't apply a transition when showing or hiding a toolbar that is fixed (not fullscreen) when the user is scrolled to the top or bottom of the viewport already. 2011-12-20 17:38:05 +07:00
scottjehl
16f73e737f removed the hideOnScrollStop option and feature - too complicated for a default option. Might be worth supporting as an extension though. 2011-12-20 17:38:05 +07:00
scottjehl
deadbe67b2 changed scrollToggle to hideOnScrollStop, which does just that. It only works if tapToggle is true, so that once hidden, the bar can be toggled visible again with a tap. 2011-12-20 17:38:05 +07:00
scottjehl
6aa3e384fe fixed the restorePageZoom method so that it does what it says on the tin. 2011-12-20 17:38:05 +07:00
scottjehl
32a2e34e07 patched up support for transition: "none" rather than false, for consistency with other uses of the option in jQM. 2011-12-20 17:38:05 +07:00
scottjehl
103f409c47 added new script and associated styles for handling "fixed" toolbars 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.
2011-12-20 17:38:05 +07:00