- From: alexelias via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 Jul 2016 19:33:49 +0000
- To: public-css-archive@w3.org
My perspective on this is that the only truly useful feature of meta viewport is "width=device-width". This tells mobile browsers to behave like desktop browsers (set layout width to size of the window). Therefore, desktop browsers "already support" the useful part of meta viewport in some sense, so there is actually almost no action we need to take here. Breaking down the other features of meta viewport: - width=[fixed number]; very rarely used (mainly ancient mobile content), enables actively non-responsive websites - height=[anything]; even more rarely used. interop is extremely poor between different mobile browsers on "height" but we treat this as a P3 bug since there is very little usage nor use cases (except non-responsive, short-height layouts) - minimum-scale, maximum-scale, initial-scale = non-1: I've never seen any use case for setting specific non-1 values of these - initial-scale=1: arguably useful to disable some mobile browsers' behavior to always zoom out to fit the content width (although this can also be addressed by simply sizing all of one's content properly). This one is moot for the same reason as width=device-width though -- setting this value to 1 makes mobile browsers behave more like desktop browsers, so there's nothing to support here on desktop. - user-scalable=no: arguably useful on desktop as well, although this can also be achieved by preventDefaulting input events (which use cases like maps which truly care about this are likely to do anyway). Another way of phrasing this is that meta viewport is largely a way to declare "I designed my site with mobile browsers in mind, therefore disable all those mobile browser quirks that exist to compensate for non-responsive legacy desktop sites, and simply behave like a normal browser". It's just another piece of header boilerplate that will be on all sites moving forward, like the HTML DTD. It doesn't provide any functionality per se, it just disables some developer-hostile interventions. -- GitHub Notification of comment by alexelias Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/258#issuecomment-230882089 using your GitHub account
Received on Wednesday, 6 July 2016 19:34:01 UTC