Karl Dubost💡 :karlcow Reporter
	Description • 8 years ago

(change the product/component adequatly if I missed something)

This issue is part of a couple of tests, I'm doing comparing Firefox Android and Chrome Android for layout differences wrt viewport values.
The tests are available at http://la-grange.net/2016/12/01/viewport/

Test 0001 - <meta name="viewport" content="width=480">

This one creates common Web compatibility issue. Firefox and Chrome does not interpret this the same way.

* Firefox sets the width to 480px. Images bigger than 480px are cut. Horizontal scroll is allowed.
* Chrome sets the width to the biggest element in the page and ignores(?) the 480px. So the user can see everything.

	Karl Dubost💡 :karlcow Reporter
	Comment 1 • 8 years ago

Firefox test-0001-fx54.0a1.20170201-and4.4.4.png
Chrome  test-0001-chr55.02883.91-and4.4.4.png

	David Bokan
	Comment 2 • 7 years ago

Hey, Chrome eng here.

This isn't actually as big a difference as it seems. The difference is that Chrome loads the page "maximally zoomed out", we try to load so that all the content width fits in the viewport. The large image causes the content width of the page to be larger than 480px so Chrome zooms out to make the whole width visible. If you zoom out on the page in Firefox the page looks identical. This is an initial-scale difference rather than layout.

	Hiroyuki Ikezoe (:hiro)
	Comment 3 • 6 years ago

Thank you, David.  Your comment helped me to understand what Chrome does.
I am now pretty sure this is a dup of bug 1423709.

	Hiroyuki Ikezoe (:hiro)
	Comment 4 • 6 years ago

Gah, the duplicate field has lost during reloading this bug. :/