CSS3/FixedPosition: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(add a few explanatory sentences)
Line 12: Line 12:
* Links
* Links
** http://www.quirksmode.org/blog/archives/2010/12/the_fifth_posit.html
** http://www.quirksmode.org/blog/archives/2010/12/the_fifth_posit.html
*** Ben's critique: web developers would need to create two elements for every position: fixed element, even if the elements behave the same on all devices. We already have media queries that can be used to not apply position: fixed.


== Patterns like fixed position ==
== Patterns like fixed position ==

Revision as of 21:09, 7 December 2010

There are a few areas where it's become clear we need to make improvements on the currently specified/implemented behavior of position:fixed:


Mobile and Tablets

The problem of zooming some content and not others.

  • Mobile effectively has two viewports: what content layout sees and what the user sees.
  • What behavior do we want to support for position: fixed on mobile devices and tablet devices? Goals:
    • Backward compatible with desktop (i.e., leaves most pages usable that weren't designed with zooming in mind)
    • ...
  • Links

Patterns like fixed position

Elements you want to scroll up and then stack up against the top of the viewport (or the inverse elements you want to scroll down and stack up against the bottom of the viewport).