W3C home > Mailing lists > Public > public-css-archive@w3.org > April 2017

[csswg-drafts] [css-device-adapt] Meta viewport tokenizer should re-use window.open() features tokenizer

From: Simon Pieters via GitHub <sysbot+gh@w3.org>
Date: Thu, 27 Apr 2017 09:55:28 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-224732039-1493286927-sysbot+gh@w3.org>
zcorpan has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-device-adapt] Meta viewport tokenizer should re-use window.open() features tokenizer ==
https://drafts.csswg.org/css-device-adapt/#parsing-algorithm

See https://bugs.webkit.org/show_bug.cgi?id=170548#c36

In https://github.com/whatwg/html/pull/2476 we specified the tokenizer for `window.open()`'s features argument, and when @cdumez worked on implementing it in WebKit he noticed that the same parser is being used for `<meta name=viewport content="...">`.

I haven't checked if the same is true in other browser engines, but it seems like a missed opportunity to let these diverge for no particular reason. So I suggest we change css-device-adapt to hook into HTML's features tokenizer, so these are consistent and to reduce implementation complexity/footprint, reduce chances for bugs, and so on. As a side-effect we're more likely to reach interop for meta viewport.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1302 using your GitHub account
Received on Thursday, 27 April 2017 09:55:35 UTC

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