Magnified website bug after exiting responsive design mode.
Categories
(DevTools :: Responsive Design Mode, defect)
Tracking
(firefox65 affected, firefox66 affected, firefox67 affected)
People
(Reporter: ong-xc, Assigned: bradwerth)
References
(Blocks 1 open bug)
Details
(Whiteboard: [dt-q])
Attachments
(1 file, 3 obsolete files)
335.91 KB,
application/x-zip-compressed
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0
Steps to reproduce:
- Magnified a page to 300%
- Enter responsive design mode.
- Magnified to 100%
- Exit responsive design mode.
Actual results:
Page stays magnified at 300%.
Expected results:
Page should de-magnified back to 100%.
Comment 1•5 years ago
|
||
Tested this issue on several machines: Windows 10, Mac OS X - Firefox versions: latest nightly 67.0a1, beta 66.0b10, and release 65.0.1 and 65.0. On all versions the issue can be reproduced. Specially, try with the Reddit and Wikipedia websites.
Comment 2•5 years ago
|
||
This seems to be related to bug 1516413, might be the same root issue but different steps to reproduce.
Assignee | ||
Comment 4•5 years ago
|
||
Assignee | ||
Comment 5•5 years ago
|
||
https://phabricator.services.mozilla.com/D23583 allows FullZoom messages to passthrough to the RDM document. The document reverts to the container zoom level when RDM is closed, but scrollbar layout is affected. Bug 1501665 will likely fix that, so blocking this bug on that landing.
Updated•5 years ago
|
Assignee | ||
Comment 6•5 years ago
|
||
Since the RDM UI is presented as UI, it makes sense for it to stay at
the same zoom level as the rest of the interface.
Depends on D23583
Assignee | ||
Comment 7•5 years ago
|
||
Depends on D25256
Assignee | ||
Comment 8•5 years ago
|
||
I'm breaking this bug into pieces since we know how to solve parts of the problem, but not yet all of the problem.
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Assignee | ||
Comment 9•5 years ago
|
||
It looks like this will be resolved totally by the fixes for Bug 1541158.
Updated•5 years ago
|
Description
•