Case: a mediaquery is used to switch layout parameters at 600px. If I
zoom page 200% that switching takes place at
300(screen)px/600(CSS-relative)px in Trident, Gecko and Presto, but at
600(screen)px/300(CSS-relative)px in WebKit. So, in the 3 former engines
the mediaquery switching is a function of page zoom, while in the last
engine it stays locked to window width and screen pixels.
I much prefer the former since it makes sense to change layout when page
is zoomed so much that content doesn't fit in window/on screen. For
instance; that SSR styles kick in and redefine layout to a 1-column when
page is zoomed so much that there isn't room for a 3-column layout with
content staying inside containers.
It also seems logical that we can reliably continue to define values in
CSS-relative pixels instead of screen-bound pixels now that screen
resolution is increasing and the resolution-spread on end-users' screens
become larger and larger.
So, what is our poor "px" supposed to be relative to these days? Zoom
factor or screen?
regards
Georg
______________________________________________________________________
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
