Recommendations for a CSS validator? The W3C validator appears to be outdated.
CSS 2.2: Where to validate it? And why W3C validator provides an option to validate 2.1 but not 2.2?
validation - Differences between validator.w3.org and jigsaw.w3.org css validator? - Stack Overflow
seo - Should I ignore W3 CSS Validation Service? - Webmasters Stack Exchange
Videos
My old standby, the W3C Validator, appears to be a bit out-of-date and doesn't support nested selectors.
I tried the csstree validator but it stops working when input contains CSS variables (e.g. --color: green).
I also tried the csstree-validator NPM package but it's choking on nested @media rules, which are a fairly recent addition.
What I'm really hoping for is an NPM package that can validate the CSS compiled by a static site generator, but even just something I could copy-paste into would be fine.
Any recommendations?
Edit: Actually, Stylelint seems like it'll do just fine, with the added advantage that we already use it in our projects for linting!
There are two questions here. I hope at least the second one is not off-topic for Stack Overflow.
The second question is very short:
Where can I validate CSS 2.2?
The first question is longer.
Could anybody explain why CSS 2.2, compared to 2.1, feels like a "second-class citizen"? For example,
the Wikipedia article about CSS mentions CSS 2.1 fifteen times, whereas CSS 2.2 only once
https://css-validator.org/ and https://jigsaw.w3.org/css-validator/ provides an option to validate 2.1, but not 2.2
According to this: https://github.com/w3c/csswg-drafts/issues/2008 discussion, CSS 2.2 is merely 2.1 with incorporated errata, but this doesn't answer why 2.2 didn't gain any traceable, on the Web, mentions.
» npm install w3c-css-validator
W3C errors (css or html) increase the chances of your site not rendering correctly across all devices.
You should worry about the css errors and get them fixed.
There is an awesome W3C Validator Chrome plugin that makes troubleshooting easy.
I would say it's good to have valid scripts. Having said that when you use third-party products it may be hard make it a valid one.
If you have a custom-designed solution then you can easily fix and make it fully valid.
So, i would say don't worry too much but if it is within your capacity to make it valid then go ahead and make one.
Modified:
As stated, it's good to have valid HTML and CSS as it makes it easier to manage. But if you are using a third-party system and if it is too hard to make it a valid one the do not worry as search engine reads incorrect markup fine.
Watch This: https://www.youtube.com/watch?v=j3KgrbiB1pc