Skip to content

test scripts should run drt with --enable-shadow-dom and --enable-style-scoped #3864

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

Closed
DartBot opened this issue Jun 25, 2012 · 3 comments
Closed
Assignees
Labels
area-test Cross-cutting test issues (use area- labels for specific failures; not used for package:test).

Comments

@DartBot
Copy link

DartBot commented Jun 25, 2012

This issue was originally filed by [email protected]


So we can write tests for ShadowDOM behavior.

@DartBot
Copy link
Author

DartBot commented Jun 25, 2012

This comment was originally written by [email protected]


To clarify: both Dartium and dart2js+Chrome tests should have the flags set, if possible.

@DartBot
Copy link
Author

DartBot commented Jun 26, 2012

This comment was originally written by [email protected]


Fixed for dartium and the dartium version of drt. Won't work with Chrome right now because our testing chrome binary isn't tip.

@sigmundch
Copy link
Member

Added Fixed label.

@DartBot DartBot added Type-Defect area-test Cross-cutting test issues (use area- labels for specific failures; not used for package:test). labels Sep 12, 2013
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-test Cross-cutting test issues (use area- labels for specific failures; not used for package:test).
Projects
None yet
Development

No branches or pull requests

2 participants