CSS syntax errors - How do I fix?

I ran my site through https://www.wpfastestcache.com/css-validator/ and there were several syntax errors (see below) which is preventing me from using several of WPFastestCache’s premium features. How do I resolve this?

https://tlufj2t1o9n423j5e3zmahfd-wpengine.netdna-ssl.com/wp-content/themes/pro/framework/dist/css/site/stacks/integrity-light.css?ver=4.0.11
Unexpected token ‘1fr’ at line 1, col 4427.
Unexpected token ‘1fr’ at line 1, col 4445.
Unexpected token ‘1fr’ at line 1, col 4525.
Unexpected token ‘1fr’ at line 1, col 4548.
Expected LBRACE at line 1, col 39747.
Unexpected token ‘)’ at line 1, col 39747.
Unexpected token ‘,’ at line 1, col 39748.
Expected LBRACE at line 1, col 39823.
Unexpected token ‘)’ at line 1, col 39823.
Unexpected token ‘,’ at line 1, col 39824.

Hello @cling,

Please use this Validator: The W3C CSS Validation Service

Thanks.

Hi Ruenel! I found several syntax errors. How can I resolve these? https://jigsaw.w3.org/css-validator/validator?uri=https%3A%2F%2Fsortable.com%2F&profile=css3svg&usermedium=all&warning=1&vextwarning=&lang=en

Hey @cling,

For the stack CSS, please contact WPFastestCache’s support to help you exclude that CSS from being cached for now. And, it should be optimized so you need to exclude that from optimization as well.

For the syntax error in the bar’s border-radius, enable the Bar’s new Border Radius option. I’ll report this in our issue tracker so this will be queued to be investigated by our dev team.

image

image

I couldn’t replicate the other errors like the accordion heading. If that is a custom CSS, please fix or remove your custom CSS codes.

I see errors coming from 3rd parties also so please contact WPFastestCache’s support to learn how to work with this or report to the plugin author.

Thanks.

Hi @cling,

I wanted to reach out to advise you that we’ve corrected the bar border radius issue for the next release. I’ve also reviewed your validation report and can confirm we have speak: none in the theme. We’ll look into those cases more closely soon. Presently, those two are the only error we’ve identified to be issues with Pro itself.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.