Closed Bug 1407582 Opened 7 years ago Closed 6 years ago

RDM does not respect <meta name="viewport" content="initial-scale=X" setting on sites containing a wide element

Categories

(DevTools :: Responsive Design Mode, defect, P3)

57 Branch
defect

Tracking

(firefox57 fix-optional, firefox58 wontfix, firefox59 ?)

RESOLVED FIXED
Tracking Status
firefox57 --- fix-optional
firefox58 --- wontfix
firefox59 --- ?

People

(Reporter: nachtigall, Unassigned)

References

(Blocks 1 open bug, )

Details

I have a page with <meta name="viewport" content="initial-scale=0.5" />. RDM does not respect this setting, that is, does not scale it.

STR:
===
1. Go to https://codepen.io/nachtigall/pen/aLKLLq 
2. Look at the page as a whole by selecting "Change View" => "Debug Mode"
3. Open RDM in DevTools
4. Select "Apple iPad Mini 2" in Portrait, that is, 768 width

AR:
===
The image is not scaled by factor 0.5

ER:
===
Like Chrome's RDM and native Firefox on Android (and Chrome on Android) do it: Scale the page (and its image) by 0.5

I am not sure if this is a dupe of Bug 1290420 because Bug 1290420 seems to more about when there is no <meta name="viewport"> at all on pages whereas this here is about the initial-scale setting.
Thanks for filing!  I would expect we'd fix this as part of doing bug 1290420, but let's keep this bug and depend on that one.  We can re-check this case when bug 1290420 is resolved.
Depends on: 1290420
Priority: -- → P3
Product: Firefox → DevTools
I am pretty sure bug 1290420 fixed some part of this issue, but still we need to fix bug 1494422 for the initial-scale.
Depends on: 1494422
D'oh.  I didn't actually look into the example in comment 0 when I commented comment 3.  Now I realized it contains a wide image element, which means we still need bug 1423709.
Depends on: 1423709
Summary: RDM does not respect <meta name="viewport" content="initial-scale=X" setting → RDM does not respect <meta name="viewport" content="initial-scale=X" setting on sites containing a wide element
This is going to be fixed by bug 1423013 completely.
Depends on: 1423013

I believe this is now fixed.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.