- From: <bugzilla@jessica.w3.org>
- Date: Mon, 18 Apr 2011 04:46:54 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12513 --- Comment #5 from Michael(tm) Smith <mike@w3.org> 2011-04-18 04:46:53 UTC --- (In reply to comment #2) > What do you need besides what's already being done in the CSSWG? > > http://dev.w3.org/csswg/css-device-adapt/ Until you posted that link here, I wasn't aware that draft was available on dev.w3.org, or that the CSS WG had any intention of taking it up as a deliverable. But I see that spec is also now listed in the CSS WG draft charter - http://www.w3.org/2010/09/CSSWG/charter.html - so it's clear now that they do intend to move it forward. So I guess that since as far as the HTML5 spec goes, since it already provides a means for registering extensions to the set of predefined name values in the spec, the main other thing that needed doing was to register this one in the WHATWG Wiki MetaExtensions page, which I've now done. But going forward, if we do want to discourage Web developers from using meta viewport, and encouraging them to use CSS instead. it may make sense to mention it in the spec. I guess it would seem odd to list it in the "Non-conforming features" part of the spec -- since the intro paragraph for that section says, "Elements in the following list are entirely obsolete, and must not be used by authors", and meta viewport isn't really obsolete. But it would make more sense if that intro read, "Elements in the following list are either entirely obsolete or have never been valid in any version of HTML, and must not be used by authors". -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Monday, 18 April 2011 04:46:55 UTC