Closed
Bug 1336292
Opened 8 years ago
Closed 6 years ago
[viewport] a fixed width on the viewport ignores bigger elements in the page.
Categories
(Core :: Panning and Zooming, defect, P3)
Tracking
()
RESOLVED
DUPLICATE
of bug 1423709
Tracking | Status | |
---|---|---|
firefox54 | --- | affected |
People
(Reporter: karlcow, Unassigned)
References
()
Details
(Whiteboard: [webcompat][gfx-noted])
Attachments
(2 files)
(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.
![]() |
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
![]() |
Reporter | |
Updated•8 years ago
|
Whiteboard: [webcompat]
Updated•8 years ago
|
Component: Graphics, Panning and Zooming → Panning and Zooming
Product: Firefox for Android → Core
Updated•8 years ago
|
OS: Unspecified → Android
Priority: -- → P3
Hardware: Unspecified → ARM
Whiteboard: [webcompat] → [webcompat][gfx-noted]
Comment 2•8 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.
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.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Comment 4•6 years ago
|
||
Gah, the duplicate field has lost during reloading this bug. :/
Resolution: FIXED → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•