Skip to content
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

Unable to publish because of CSS validator issues #2845

Closed
marcoscaceres opened this issue Apr 17, 2020 · 1 comment · Fixed by #2846
Closed

Unable to publish because of CSS validator issues #2845

marcoscaceres opened this issue Apr 17, 2020 · 1 comment · Fixed by #2846

Comments

@marcoscaceres
Copy link
Member

Echidna is upset :(

✗ Echidna failed to publish https://w3c.github.io/screen-orientation/W3CTRMANIFEST
 for the following reasons:

   The file has been retrieved.
   The metadata have been extracted.
   The document failed Specberus.
 👎 Unknown pseudo-element or pseudo-class “:absolute”
     ⮡ cf https://www.w3.org/pubrules/doc/rules/?profile=WD#cssValide
 👎 Unknown pseudo-element or pseudo-class “:var”
     ⮡ cf https://www.w3.org/pubrules/doc/rules/?profile=WD#cssValide
 👎 Unknown pseudo-element or pseudo-class “:var”
     ⮡ cf https://www.w3.org/pubrules/doc/rules/?profile=WD#cssValide
 👎 Unknown pseudo-element or pseudo-class “:var”
     ⮡ cf https://www.w3.org/pubrules/doc/rules/?profile=WD#cssValide

More details are available here:

 https://labs.w3.org/echidna/api/status?id=a38b65b6-b664-4b0c-9fbd-d77d6d6c2754

If you think you found a bug, please fill in and submit this issue:

 https://github.com/w3c/echidna/issues/new?title=Bug:%20%5BWHAT%5D&body=%5BEXPLANATION%5D%0A%0AFound%20while%20trying%20to%20publish%20%60https%3A%2F%2Fw3c.github.io%2Fscreen-orientation%2FW3CTRMANIFEST%60%20(see%20the%20%5Bpublication%20job%5D(https%3A%2F%2Flabs.w3.org%2Fechidna%2Fapi%2Fstatus%3Fid%3Da38b65b6-b664-4b0c-9fbd-d77d6d6c2754)).&labels=from-template

~ 4/17/2020, 1:47:39 AM
@sidvishnoi
Copy link
Member

CSS Custom properties are not yet supported with CSS validator w3c/css-validator#173 😞
I'll send a PR to remove our use of custom properties until it is supported. Would need to incorporate it in our frozen w3c-common profile also. 😞

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

Successfully merging a pull request may close this issue.

2 participants