Re: [css-om] Issues with width and resolution media queries

> > For mobile browsers, that always take up the full screen width, the
> > distinction is pointless. Ideal viewport === width of screen in unscaled
> CSS
> > pixels.
>
> It is not for height. The initial (before viewport adaptation, coming
> from fallback 980px layout or the viewport meta, etc) viewport width
> is usually === screen width because most mobile browsers do not have
> any chrome horizontally, they usually do vertically though.
>

In all mobile browsers, the height of the ideal viewport pretends the
browser chrome isn't there.


> > - In order to do so, they should use the
> > document.documentElement.clientWidth value for the width media query,
> like
> > the mobile browsers do.
>
> You know that there is no code difference here for Chrome on desktop
> and Chrome on mobile. You can check the code yourself.
>

Nonsense. Chrome on Android uses document.documentElement.clientWidth, and
Chrome on desktop uses window.innerWidth.


> There is no reason that desktop browsers cannot support both, and IE
> does in Metro mode and so does Chrome on the Pixel or the new Acer
> C720P, and maybe even on Windows? You will see pinch zoom coming to
> more and more desktop browsers, while still having page zoom support
> as well.
>

This is interesting. I didn't know about the Pixel.

Now the question is: is it possible for a user to zoom in using both kinds
of zoom simultaneously, without changing settings or anything?

And if it is, should both kinds of zoom trigger the same response? That is,
should a 200% zoom cause a DPR of 2, no matter what kind of zooming the
user uses?

If it should, mobile browsers should also change their DPR on pinch zoom.
If it should not, the two kinds of zoom should be treated in separate
properties, media queries etc.


-- 
--------------------------------------------
ppk, mobile platform strategist
http://quirksmode.org/about/
+.31.6.29585782
--------------------------------------------