Closed
Bug 1198839
Opened 10 years ago
Closed 10 years ago
MobileViewportManager should not create a displayport if there wasn't one already
Categories
(Core :: Layout, defect)
Core
Layout
Tracking
()
RESOLVED
FIXED
mozilla43
| Tracking | Status | |
|---|---|---|
| firefox43 | --- | fixed |
People
(Reporter: kats, Assigned: kats)
References
Details
Attachments
(1 file)
|
1.42 KB,
patch
|
botond
:
review+
|
Details | Diff | Splinter Review |
In https://bugzilla.mozilla.org/show_bug.cgi?id=1178847#c19 we discussed the fact that TabChild set a displayport and that we wanted to carry that behaviour over into MobileViewportManager. However the investigation on bug 1194876 showed that the MVM introduced a new behaviour inadvertently - it sets displayport margins on the root content document in the B2G parent process when there wasn't one before (and which is probably not needed).
We should update MVM to only *update* the displayport if there was one already, rather than unconditionally set one.
|
Assignee | |
Comment 1•10 years ago
|
||
|
|
Assignee | |
Comment 2•10 years ago
|
||
Attachment #8653035 -
Flags: review?(botond)
|
||
Updated•10 years ago
|
Attachment #8653035 -
Flags: review?(botond) → review+
|
||
Comment 4•10 years ago
|
||
Status: NEW → RESOLVED
Closed: 10 years ago
status-firefox43:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla43
You need to log in
before you can comment on or make changes to this bug.
Description
•