You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, reftests aren't working for Chrome android because there's no concept of resizing the window.
We should at least either either ignore or work around this issue, possibly by hacking in a zoom modification in lieu of the ability to resize the window itself? @Hexcles
While the required window size isn't met by android, we'd still get some value from being able to produce the screenshots.
Possibly related to #8571, though we don't have infra coverage for Android anyway.
The text was updated successfully, but these errors were encountered:
There's no way to resize a window on Android, but we most likely need to reset the zoom level to 100% to make sure the screenshots are meaningful, comparable and stable. However, it seems like WebDriver specs has no mentioning of zoom level.
I'm looking at document.body.style.zoom, which is unfortunately a Blink/WebKit-only API but perhaps can be justified to use here.
Zoom could and should be easily added to WebDriver.
Note that running reftests on mobile has some interesting challenges. For example you need to ensure that the device pixel ratio is set to 1, even though phones usually have a very different value. Getting the viewport to be the expected size is also a problem. Gecko basically has some special settings that afiak are only used for reftests that allow creating a document with the correct size and getting a screenshot of the full document independent of the actual device size.
Right now, reftests aren't working for Chrome android because there's no concept of resizing the window.
We should at least either either ignore or work around this issue, possibly by hacking in a zoom modification in lieu of the ability to resize the window itself? @Hexcles
While the required window size isn't met by android, we'd still get some value from being able to produce the screenshots.
Possibly related to #8571, though we don't have infra coverage for Android anyway.
The text was updated successfully, but these errors were encountered: