Skip to content

[css-writing-modes] Missing Testcases #1792

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
fantasai opened this issue Sep 9, 2017 · 3 comments
Closed

[css-writing-modes] Missing Testcases #1792

fantasai opened this issue Sep 9, 2017 · 3 comments

Comments

@fantasai
Copy link
Collaborator

fantasai commented Sep 9, 2017

Need to make sure we have tests for these:

https://lists.w3.org/Archives/Public/www-style/2017May/0002.html
https://lists.w3.org/Archives/Public/www-style/2015Sep/0326.html

(I suppose WPT has some process for tracking such things as missing coverage but until it's documented in http://web-platform-tests.org/ I'm just going to assume it doesn't exist.)

@frivoal
Copy link
Collaborator

frivoal commented Jan 5, 2018

@fantasai regarding https://lists.w3.org/Archives/Public/www-style/2015Sep/0326.html :

We already have this test: https://github.com/w3c/web-platform-tests/blob/master/css/css-writing-modes/writing-mode-parsing-svg1-001.html which checks that the legacy svg values compute to the right thing. I've just created web-platform-tests/wpt#8931 loosely based on the file you attached to https://lists.w3.org/Archives/Public/www-style/2015Sep/0326.html to also check that this aliasing mechanism isn't messing with bidi. Do you think we need anything more for this topic? (I'll look into the other mail separately).

@frivoal
Copy link
Collaborator

frivoal commented Jan 5, 2018

@frivoal
Copy link
Collaborator

frivoal commented Jan 28, 2018

Test cases merged, closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants