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.
Created attachment 8653035 [details] [diff] [review] Patch
Attachment #8653035 - Flags: review?(botond)
Status: NEW → RESOLVED
Last Resolved: 3 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.