From 0062f6c18595dfdffb3af970d120f05436c64217 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jonas=20Sch=C3=A4fer?= Date: Thu, 7 Jan 2021 11:59:59 +0100 Subject: [PATCH] Use comma instead of semicolon to separate k/v-pairs in viewport meta MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit While a draft "standard" of the CSS Working Group of the W3C (as much as any W3C "living document" is a "standard" in any meaning of the word) says in a (non normative) section that both semicolon and comma are allowed [1], the MDN has the following thing to say [2]: > To mitigate this problem of virtual viewport […], Apple introduced > the "viewport meta tag" […]. Apple's documentation does a good job > explaining how web developers can use this tag, but we had to do > some detective work to figure out exactly how to implement it in > Fennec. For example, Safari's documentation says the content is a > "comma-delimited list," but existing browsers and web pages use > any mix of commas, semicolons, and spaces as separators. This leaves us to believe that although some W3C document says that both are ok, comma is the more portable choice. [1]: https://drafts.csswg.org/css-device-adapt/#viewport-meta [2]: https://developer.mozilla.org/en-US/docs/Web/HTML/Viewport_meta_tag --- xep.xsl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xep.xsl b/xep.xsl index 6c5f8b65..504e1435 100644 --- a/xep.xsl +++ b/xep.xsl @@ -191,7 +191,7 @@ content: "XEP-"; viewport - width=device-width; initial-scale=1.0; maximum-scale=2.0 + width=device-width, initial-scale=1.0, maximum-scale=2.0