- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 Jul 2016 00:58:27 +0000
- To: public-css-archive@w3.org
Yes, the web totally depends on it, there is a lot of interoperability, it should be specified, and the css-device-adapt spec looks like a good place to do it. Even though the syntax of the viewport tag isn't CSS, what it affects is absolutely in scope, so that's good. That also lets us say what happens if you use both. The current informative definition probably needs some extra scrutiny before we can simply turn it into being normative, but it's a decent start. There's one thing I am not sure about: in #258 (and the follow up conversation that's should happen in #326 & #327), there have been questions that @viewport shouldn't have nearly as many features than it currently does, and that maybe it needs to be parred down to only `with:auto` or `min-width: <lenght>`. The current definition of @viewport is featurefull enough that we can express the viewport tag in terms of @viewport. If we do the simplification, that will no longer be true though. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/331#issuecomment-233810137 using your GitHub account
Received on Wednesday, 20 July 2016 00:58:34 UTC