Issue 139428 in chromium: Chrome for Android shows error: Viewport argument key "" not recognized and ignored.

[chro...@googlecode.com]

Status: Unconfirmed
Owner: ----
CC: android-...@chromium.org
Labels: OS-Android Pri-3 Hotlist-Upstream-Android Type-Cleanup

New issue 139428 by ls...@google.com: Chrome for Android shows error:
Viewport argument key "" not recognized and ignored.
http://code.google.com/p/chromium/issues/detail?id=139428

I am using remote devtools, and spotted an error shown in the console:
Viewport argument key "" not recognized and ignored.

What does the key "" mean here?

The page has the following meta tag:
<meta name="viewport" content="width=device-width; initial-scale=1.0;
maximum-scale=1.0; user-scalable=0;">

[chro...@googlecode.com]

Comment #1 on issue 139428 by galdor.t...@gmail.com: Chrome for Android

shows error: Viewport argument key "" not recognized and ignored.
http://code.google.com/p/chromium/issues/detail?id=139428

The spec says you should use commas, not semicolons[1]. Do you still get
the error if you change that?

[1] http://dev.w3.org/csswg/css-device-adapt/#parsing-algorithm

[chro...@googlecode.com]

Updates:
Status: Untriaged
Cc: joh...@chromium.org ael...@chromium.org
Labels: -Hotlist-Upstream-Android -Type-Cleanup Type-Bug Area-WebKit
WebKit-Core Feature-TabContents

Comment #2 on issue 139428 by srika...@chromium.org: Chrome for Android

shows error: Viewport argument key "" not recognized and ignored.
http://code.google.com/p/chromium/issues/detail?id=139428

Is this on the current revision of Chrome for Android available on Play
(18.0.1025123)?

Technically it should be handling semi colons in the viewport tags properly
/ not triggering the errors above.

[chro...@googlecode.com]

Comment #3 on issue 139428 by ls...@google.com: Chrome for Android shows

error: Viewport argument key "" not recognized and ignored.
http://code.google.com/p/chromium/issues/detail?id=139428

Yes, it is 18.0.1025123.

[chro...@googlecode.com]

Comment #4 on issue 139428 by joh...@chromium.org: Chrome for Android shows

error: Viewport argument key "" not recognized and ignored.
http://code.google.com/p/chromium/issues/detail?id=139428

Does the error go away if you remove the trailing semi-colon?

[chro...@googlecode.com]

Comment #5 on issue 139428 by ls...@google.com: Chrome for Android shows

error: Viewport argument key "" not recognized and ignored.
http://code.google.com/p/chromium/issues/detail?id=139428

After play around with comma and semi colons, I found that the problem is
the last ";" or "," that causes this key "" issue. Thanks.

[chro...@googlecode.com]

Comment #6 on issue 139428 by ls...@google.com: Chrome for Android shows

error: Viewport argument key "" not recognized and ignored.
http://code.google.com/p/chromium/issues/detail?id=139428

Yes, the error goes away if I remove the trailing semi-colon?

[chro...@googlecode.com]

Updates:
Cc: pe...@chromium.org aba...@chromium.org

Comment #7 on issue 139428 by joh...@chromium.org: Chrome for Android shows

error: Viewport argument key "" not recognized and ignored.
http://code.google.com/p/chromium/issues/detail?id=139428

Ok, so I'd recommend you use commas instead of semi-colons and remove the
trailing semi-colon (or trailing comma). All browser support commas, but
not all support semi-colons.

On our side, we should probably make the error message clearer when you
have a trailing comma/semi-colon (or remove it completely, but there is
value in warning against it since a browser that doesn't support
semi-colons will treat "width=device-width;" differently
to "width=device-width", so we should be encouraging authors not to leave
trailing commas/semi-colons).

[chro...@googlecode.com]

Comment #9 on issue 139428 by srika...@chromium.org: Chrome for Android

shows error: Viewport argument key "" not recognized and ignored.
http://code.google.com/p/chromium/issues/detail?id=139428

Thx for the clarifications on #7. Lets track this as a refinement bug
leaving it as a Pri-3 for now given there is a documented workaround.

[chro...@googlecode.com]

Comment #10 on issue 139428 by galdor.t...@gmail.com: Chrome for Android

shows error: Viewport argument key "" not recognized and ignored.
http://code.google.com/p/chromium/issues/detail?id=139428

I think it would even be a good idea to warn about semicolons, to help
developers write more compatible code. The default Android browser for
example does not implement them as separators, so if you develop with
Chromium and get warnings, is's your choice to ignore them, but at least
you know about that potential problem.
Should i file a new issue for this feature?