732975 - [maple] actual display port is not accessible in java

Status: RESOLVED FIXED

(Firefox for Android Graveyard :: General, defect)

Description

[Kartikaya Gupta (email:[e-mail])]

Currently, when setting the display port, Java tells browser.js what the desired display port margins are. browser.js then clips those margins so that they don't leak outside the page dimensions, and also adjusts them so that any clipped margin area allows the margins on the other axis to get expanded. This is done mostly because Java doesn't always have the latest-and-greatest page dimensions, and cannot do this itself.

However, this poses a problem because it makes the aboutToCheckerboard() code slightly less accurate (might result in Java thinking we're about to checkerboard when we're not) and also prevents us from drawing the checkerboard properly (bug 732756). We should fix this so that Java has the newest page dimensions and can itself calculate the desired final displayport, so that the information is available to use.

Comment 1

[Kartikaya Gupta (email:[e-mail])]

Fixed as part of bug 732564. GeckoLayerClient.getDisplayPort() now provides an accurate display port relative to the page top-left, in device pixels (i.e. CSS pixels multiplied by zoom).