1632020 - no content meta viewport tag should be ignored

Status: RESOLVED FIXED

(Core :: DOM: Core & HTML, defect, P2)

Description

[Hiroyuki Ikezoe (:hiro)]

In bug 1498729 we introduced a machinery that if there are multiple meta viewport tags, the content of the last modified meta viewport tag is used. But it looks like Chrome doesn't use the content if the meta viewport tag doesn't have content attribute, i.e. <meta name="viewport">.

Comment 1

[Hiroyuki Ikezoe (:hiro)]

To be more precise, Chrome handles <meta name="viewport" content=""> as a valid viewport tag.

Comment 2

[Hiroyuki Ikezoe (:hiro)]

Attachment: A test case I used for checking Chrome's result

Modified a test case by David Bokan. http://bokand.github.io/20701.html

Comment 3

[Hiroyuki Ikezoe (:hiro)]

Attachment: Bug 1632020 - Don't handle no content attribute meta viewport tag. r?smaug

That's what Chrome does basically and it does quite make sense. But in the test
case of test_meta_viewport_removing_content_attribute.html which removes a valid
content attribute, Chrome uses the removed content, which seems a bug in Chrome
I've reported before [1], and I believe we shouldn't mimic the bug.

[1] https://bugs.chromium.org/p/chromium/issues/detail?id=986674

Comment 4

[Hiroyuki Ikezoe (:hiro)]

Filed a spec issue. https://github.com/w3c/csswg-drafts/issues/4995

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/7bb67169c8da
Don't handle no content attribute meta viewport tag. r=smaug

Comment 6

[Cristian Brindusan [:cbrindusan]]

https://hg.mozilla.org/mozilla-central/rev/7bb67169c8da