MobileViewportManager should not create a displayport if there wasn't one already

RESOLVED FIXED in Firefox 43

Status

()

RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: kats, Assigned: kats)

Tracking

unspecified
mozilla43
Points:
---

Firefox Tracking Flags

(firefox43 fixed)

Details

Attachments

(1 attachment)

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.
Attachment #8653035 - Flags: review?(botond) → review+
https://hg.mozilla.org/mozilla-central/rev/501ea1317fb5
Status: NEW → RESOLVED
Last Resolved: 4 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.