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

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

From: alexelias via GitHub <sysbot+gh@w3.org>
Date: Fri, 08 Jul 2016 19:33:18 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-231452296-1468006396-sysbot+gh@w3.org>
I am open to proposals like `@viewport`, but I perceive it emerges 
less out of any use case than the general feeling that `meta viewport`
 is a mess that should be cleaned up.  And I agree it's a mess.  In 
meta viewport crazy land:
- `width=` means `min-width=`
- `device-width` means `window-width`
- `initial-scale` doesn't only affect initial scale but also has weird
 side effects on the width
- `height` doesn't really mean anything
- the existence of the tag also "randomly" disables behaviors like tap
 disambiguation menu and double-tap zoom delay
- and all this only does anything at all on "mobile browsers", which 
is an increasingly hazily defined category of UAs.

The problem is: does trying to clean the mess by adding a new thing 
actually help matters at all, or is it just another case of 
https://xkcd.com/927/?  And in practice, it does seem like most 
webdevs can get by simply knowing the "best practice" of slapping 
`<meta name="viewport" content="width=device-width">` on all their 
pages (given a responsively designed site) and not really think too 
hard about it any further.  That's why I'm currently leaning towards 

GitHub Notification of comment by alexelias
Please view or discuss this issue at 
using your GitHub account
Received on Friday, 8 July 2016 19:33:26 UTC

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