W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2016

Re: [csswg-drafts] [css-device-adapt] @viewport is preloader-hostile

From: Peter-Paul Koch via GitHub <sysbot+gh@w3.org>
Date: Tue, 12 Jul 2016 09:44:13 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-231990547-1468316652-sysbot+gh@w3.org>
In my opinion we should keep the current meta viewport tag, warts and 
all. As @alexelias argued, it already does what we want, and even 
though its syntax (and the fact that it's a tag) is not optimal, web 
developers and browser vendors are used to it and it already solves 
most of our problems.

I feel that this discussion fails to distinguish between two slightly 
different widths:

1. The min-width of the layout viewport
2. The initial width of the canvas that's actually visible once the 
browser finished initial zooming (or not)

The second one is the real problem, I think. The first one is already 
solvable right now.

What should happen when content flows out of the layout viewport 
horizontally? In other words, should the visible canvas be extended 
beyond the layout viewport or not? I did some research ages ago 
(http://www.quirksmode.org/blog/archives/2014/01/widthdevicewidt.html)
 and concluded that browsers are all over the place.

Maybe it would be a good idea to define what exactly should happen 
when content overflows. Should the browser zoom out in order to show 
all of it, or should it accept that the content is not fully visible? 
There are arguments to be made for both, and I'm not sure which 
scenario I'd support. Or should we leave this to individual browsers 
after all? I'd love to hear some opinions on that.

In any case, this is a question of what the initial width of the 
visible canvas should be. Equal to the layout viewport, or equal to 
the largest element if that element is larger than the layout 
viewport?

As to @frivoal 's point of overlapping or squeezed elements, that's 
caused by web developers not using a min-width for the layout 
viewport, and is solvable with the tools we have today. Adding a 
layout viewport min-width is already possible (though not intuitive) 
with the current meta viewport.

`<meta name="viewport" content="width=400px,initial-scale=1">`

Now 400px is the min-width of the layout viewport in all browsers 
except for Android WebKit. (Unless things changed significantly since 
my last full test run.)

Since this is not common knowledge I thought I'd mention it, even 
though I wouldn't be surprised if most participants already know this.

Maybe this should become common knowledge. It would help a bit with 
layout viewport min-width and squeezed elements, though it wouldn't 
solve the problem of the visible canvas initial width.

-- 
GitHub Notification of comment by pp-koch
Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/258#issuecomment-231990547 
using your GitHub account
Received on Tuesday, 12 July 2016 09:44:22 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:00 UTC