Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support changing the viewport size in non-servo executors #7135

Open
wpt-issue-mover opened this issue Aug 31, 2017 · 3 comments
Open

Support changing the viewport size in non-servo executors #7135

wpt-issue-mover opened this issue Aug 31, 2017 · 3 comments
Labels
infra priority:backlog type:untestable wptrunner The automated test runner, commonly called through ./wpt run

Comments

@wpt-issue-mover
Copy link

Originally posted as w3c/wptrunner#166 by @Ms2ger on 30 Dec 2015, 16:24 UTC:

@wpt-issue-mover
Copy link
Author

Originally posted as w3c/wptrunner#166 (comment) by @gsnedders on 21 Mar 2017, 17:32 UTC:

It's probably worth splitting out the dpi stuff into a separate issue, as that's more obscure, IMO. (i.e., we probably need viewport size support post csswg-test merge as we try and sort out an even bigger case of #4619).

@wpt-issue-mover
Copy link
Author

Originally posted as w3c/wptrunner#166 (comment) by @gsnedders on 21 Mar 2017, 17:50 UTC:

Okay, split that into w3c/wptrunner#240.

@gsnedders
Copy link
Member

Is this something we still want to pursue? It would make importing tests from Gecko's reftest runner easier (given they have a 800x1000 viewport), and deal with the large backlog of overlarge tests (see #5403).

cc/ @Hexcles @jgraham @dbaron @thejohnjansen @youennf

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infra priority:backlog type:untestable wptrunner The automated test runner, commonly called through ./wpt run
Projects
None yet
Development

No branches or pull requests

3 participants