Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Benjamin Intal

    (@bfintal)

    Hello, thanks for posting!

    Regarding the CSS parse errors on the optimized CSS, they seem to be false positives because they look to be valid CSS (at least for the CSS which are outputted by Stackable) – I’m not sure about why they are pointed as errors though, but I saw that validation sometimes reports these things, maybe because of CSS optimizations.

    Thanks for the report about the incorrect divs, we’ll add this to our list of todos that we will address in a future update. The good thing is that these validation errors don’t have any immediate, critical impact on the website’s functionality or appearance.

    Thanks!

    Thread Starter septero

    (@septero)

    Hi @bfintal,

    Thanks for answer and clarification that CSS parse errors have no impact on the functionality or appearance of the website. I’m waiting for the div bug to be fixed. I mark this topic as solved.

    Best regards

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘W3C Validation errors’ is closed to new replies.