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

Need a mechanism to set DRT/browser flags on a per test basis. #4502

Closed
vsmenon opened this issue Aug 14, 2012 · 4 comments
Closed

Need a mechanism to set DRT/browser flags on a per test basis. #4502

vsmenon opened this issue Aug 14, 2012 · 4 comments
Labels
area-infrastructure closed-obsolete Closed as the reported issue is no longer relevant

Comments

@vsmenon
Copy link
Member

vsmenon commented Aug 14, 2012

I'm writing a new test where I need --allow-external-pages set on DRT (xhr_cross_origin_test). I'd rather not set globally.

We could use this to set allow-file-access-from-files, enable-shadow-dom, and other flags that are off by default but useful for testing.

@ricowind
Copy link
Contributor

Vijay: How do you propose we do this, and which tests are you talking about?


Removed Area-Test label.
Added Area-Infrastructure label.

@vsmenon
Copy link
Member Author

vsmenon commented Nov 21, 2013

Not sure anything is blocked on this any more. We've added a test server in the loop since and enabled some other flags by default in Dartium.


cc @blois.

@blois
Copy link
Contributor

blois commented Nov 22, 2013

@ricowind
Copy link
Contributor

ricowind commented Jun 2, 2015

Added AssumedStale label.

@vsmenon vsmenon added Type-Defect area-infrastructure closed-obsolete Closed as the reported issue is no longer relevant labels Jun 2, 2015
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-infrastructure closed-obsolete Closed as the reported issue is no longer relevant
Projects
None yet
Development

No branches or pull requests

3 participants