W3C home > Mailing lists > Public > public-css-archive@w3.org > August 2020

Re: [csswg-drafts] [css-variables-1] CSS Variables should be considered as released. (#5390)

From: Michael[tm] Smith via GitHub <sysbot+gh@w3.org>
Date: Thu, 06 Aug 2020 01:23:00 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-669628187-1596676979-sysbot+gh@w3.org>
> Again, tho, the W3C validator, which I linked above, handles variables and custom properties just fine.

The reason that W3C validator handles variables and custom properties is that for CSS checking, it’s using a fork I made of the W3C CSS validator backend — a fork with a patch for handling variables and custom properties.

But that patch in its current form isn’t really suitable for upstreaming to the W3C CSS validator sources — so I think the W3C CSS validator service at https://jigsaw.w3.org/css-validator/ doesn’t actually yet handle variables and custom properties.

That’s one reason why I recommend that these days anybody who wants to do CSS validation should consider trying https://validator.w3.org/nu/ (the Nu Checker) as an alternative to https://jigsaw.w3.org/css-validator/.

If you give https://validator.w3.org/nu/ the URL for a CSS stylesheet, or upload a .css file to it, it’ll recognize it as CSS and check it (using an embedded version of the backend of the W3C CSS validator, except with one difference being, as I mentioned above, that it’s able to handle variables and custom properties).



-- 
GitHub Notification of comment by sideshowbarker
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5390#issuecomment-669628187 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 6 August 2020 01:23:02 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:13 UTC