Validator returns "Congratulations! No Error Found." for CSS with syntax errors in it
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 250
- Forks
- 123
- PR merge metrics
- No merged PRs in 30d
Description
The following CSS validates correctly:
b {text-decoration: underline solid black;}
/* .disabled-attribute{display: block;} */ %
!
)
/* .another > .disabled > .attribute {box-shadow: 10px 10px 20px RGBA(255,255,255,0);border: 1px solid hsla(0,0%,100%,.2) !important;} */
span.greentext {color: green;}
Instead of reporting the error when it encounters the invalid characters, it simply stops validating and reports that the CSS is valid.
I've put together a working example of this at https://github.com/kupietools/W3C-CSS-validation-bug.
Contributor guide
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 the CSS from the issue, or the working example at https://github.com/kupietools/W3C-CSS-validation-bug, through the CSS validator and observe where validation stops. Trace the Java validation entry point that handles the invalid characters. Done means the validator reports the syntax errors instead of returning “Congratulations! No Error Found.”
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100