Webrender clips viewport with Responsive Design Mode meta viewport on
Categories
(Core :: Graphics: WebRender, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox-esr68 | --- | unaffected |
firefox67 | --- | unaffected |
firefox68 | --- | unaffected |
firefox69 | + | wontfix |
firefox70 | + | verified |
People
(Reporter: rdoghi, Assigned: botond)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression)
Attachments
(2 files)
[Affected versions]:
Nightly 69.0a1
[Affected platforms]:
Platforms: ALL
Prerequisites:
Access FF and enter in about:config
Type devtools.responsive.metaViewport.enabled and set the value to "true"
Type gfx.webrender.all set to "true" and verify about:support for Composition (Webrender)
Steps :
- Launch the Firefox browser and reach www.facebook.com and zoom to 150%
- Hit Ctrl + Shift + M in order to start Responsive Design Mode.
- Enable touch Simulation.
Expected Results :
The page should be displayed properly with touch simulation enabled.
Actual Results :
The page seems cropped in RDM mode.
Notes:
With Webrender ON and Viewport ON this issue can be reproduced as soon as the user enables touch simulation in RDM.
With Webrender Off and Viewport ON or Viceversa this issue does not reproduce.
Please also note that on some Systems where Webrender is unsupported and the Composition just says Basic The issue occurs when the user Exits RDM not when RDM is on.
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Comment 1•5 years ago
|
||
Comment 2•5 years ago
|
||
This will need attention from the WebRender team.
Comment 3•5 years ago
|
||
This will probably be fixed by the same thing that fixes bug 1520096.
Updated•5 years ago
|
Comment 5•5 years ago
|
||
The regressor landed in 69 and 68 is marked as unaffected, so 67 should be unaffected.
Updated•5 years ago
|
Comment 6•5 years ago
|
||
The priority flag is not set for this bug.
:dholbert, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 7•5 years ago
|
||
This seems to be in the wrong component. Someone from the WebRender team should triage.
Comment 8•5 years ago
•
|
||
Hmm, I'll bet this will be fixed by the patch in bug 1563717, based on bug 1563717 comment 7.
Updated•5 years ago
|
Comment 9•5 years ago
|
||
Changing the priority to p1 as the bug is tracked by a release manager for the current beta.
See What Do You Triage for more information
Comment 10•5 years ago
|
||
assigning to Botond for now since it looks like this will be fixed by: bug 1563717
Comment 11•5 years ago
|
||
Confirmed this was fixed by bug 1563717.
Reporter | ||
Comment 12•5 years ago
|
||
This issue still occurs When the user Exits RDM, I have also left a comment on Bug 1563717 so we can keep a better track of this issue. Please let us know if we should log a new issue for it. I'll attach the current behavior here as well.
Reporter | ||
Comment 13•5 years ago
|
||
Comment 14•5 years ago
|
||
Can you please open a new bug for the issue?
Updated•5 years ago
|
Reporter | ||
Comment 15•5 years ago
|
||
This issue is Verified as Fixed in Nightly 70.0a1 (2019-07-29) based on the steps from the Description.
Reporter | ||
Comment 16•5 years ago
|
||
I have added a new issue Bug 1569626 as requested in Comment 14.
Assignee | ||
Updated•5 years ago
|
Comment 17•5 years ago
|
||
Same as bug 1563717.
Reporter | ||
Comment 18•4 years ago
|
||
Since This is a wontfix for 69 we can update the flags accordingly.
Updated•2 years ago
|
Description
•