w3c / w3c/css-validator-testsuite
Failing tests at https://jigsaw.w3.org/css-validator/autotest/client/sample.html
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 6
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
These tests are failing, both when:
- invoked through your https://jigsaw.w3.org/css-validator/autotest/client/sample.html
- invoked with the patched autotest at w3c/css-validator#486 (ie. at the command line, with
ant autotest)
List of test:
testsuite/properties/positive/overflow-wrap/css3/001.css
testsuite/properties/positive/text-decoration/css3/001.css
testsuite/properties/positive/text-justify/css3/001.css
testsuite/properties/positive/text-underline-position/css3/001.css
testsuite/properties/positive/transform-origin/css3/001.css
testsuite/properties/positive/vertical-align/css3/001.css
testsuite/properties/positive/word-spacing/css3/001.css
testsuite/properties/positive/line-height/css3/001.css
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running ant autotest and reproducing the failures through the linked sample.html. Inspect the eight listed CSS files and their autotest results; done means those tests pass both from the command line and through the web sample.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100