-
Notifications
You must be signed in to change notification settings - Fork 27
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
Some interop-2022-cascade tests cover too many things #74
Comments
see also #5 I think we basically just want to use |
@xiaochengh do you think these tests can be split (perhaps using variants) or use |
Discussed in #77. General preference is that we split the tests if at all possible. Using |
Is there a list of tests we'd like to split, and a guideline how to split them? |
@xiaochengh See the first comment, essentially css/css-cascade/layer-statement-before-import.html and css/css-cascade/layer-cssom-order-reverse.html |
The tests were split in web-platform-tests/wpt#34081. Thanks @xiaochengh! |
This one tests
document.adoptedStylesheets
which WebKit does not implement: https://wpt.fyi/results/css/css-cascade/layer-statement-before-import.html?label=master&label=experimental&product=chrome&product=firefox&product=safari&aligned&q=label%3Ainterop-2022-cascadeThis one tests
@property
: https://wpt.fyi/results/css/css-cascade/layer-cssom-order-reverse.html?label=master&label=experimental&product=chrome&product=firefox&product=safari&aligned&q=label%3Ainterop-2022-cascadeWorth splitting or removing those tests from Interop 2022
The text was updated successfully, but these errors were encountered: