2010 css errors and warnings (validation)

  • marthalee

    (@marthalee)


    15 years, 9 months ago

    I’ve built a site in 3.0 and have modified the style.css and the sidebar.php files of 2010 as a child theme. The site validates as HTML 5 (after I turned off a plugin, that is), but it has a boatload of CSS errors and warnings. 14 CSS errors in parts of the file I did not touch (box-shadow stuff, last-child stuff, size-adjust stuff. A bunch of it is, I believe, CSS 3 (a yet un-“released” standard). And then 47 instances of color and background color the same–which is just how to get the search engines suspicious of you. I can go in and fix all this stuff. I need a site that validates now, not in a few years, so I guess I will. ….

Viewing 11 replies - 1 through 11 (of 11 total)
  • Thread Starter marthalee

    (@marthalee)

    15 years, 9 months ago

    OK, lest you think my complaint is that I have screwed up my theme, I changed my theme back to Twenty ten. Virgin style.css, straight from WordPress.org.

    CSS validation from W3C: 14 errors and 81 warnings!

    Why????

    esmi

    (@esmi)

    15 years, 9 months ago

    The errors relate to CSS 3 specific properties – the validator defaults to CSS 2.1 only. Try re-validating as CSS 3.

    Thread Starter marthalee

    (@marthalee)

    15 years, 9 months ago

    Yes. The W3C validator does not validate for CSS 3. Do you know of a validator that will assess for CSS 3?

    Moderator James Huff

    (@macmanx)

    15 years, 9 months ago

    At the W3C CSS validator, click the “More Options” link and select “CSS level 3” from the “Profile” pull-down menu.

    Thread Starter marthalee

    (@marthalee)

    15 years, 9 months ago

    Thanks! Don’t know how I missed that big “more options” link… duh.

    Moderator James Huff

    (@macmanx)

    15 years, 9 months ago

    You’re welcome!

    Thread Starter marthalee

    (@marthalee)

    15 years, 8 months ago

    Well, the same vendor prefixes that don’t validate as CSS 2.1 also don’t validate as CSS 3.

    Rev. Voodoo

    (@rvoodoo)

    15 years, 8 months ago

    vendor specific css properties don’t validate at all AFAIK. I don’t think they ever will. But they work, so it’s still nice to use them as long as they degrade gracefully……

    Thread Starter marthalee

    (@marthalee)

    15 years, 8 months ago

    OK, well I’ve read Eric Meyer’s article on vendor tags on A List Apart, and my zeal for web standards has gotten a little more flexible.

    BUT, I’ve been using the validators not only to check for (“real”) errors in my own code, but also to reassure potential clients (who are likely either new to the idea of standards or not very sophisticated about them).

    So it doesn’t exactly work to put links to the W3C validators–only to have them return error messages. Are there alternate validation services in which WP 3.0 and Twenty Ten actually validate???

    Rev. Voodoo

    (@rvoodoo)

    15 years, 8 months ago

    Are there alternate validation services in which WP 3.0 and Twenty Ten actually validate???

    I’ve not searched exhaustively, I’ll admin. However, I haven’t found one. I believe the options are to get good at explaining why the css validation isn’t an issue, or to remove the vendor specific code from client site”s unfortunately

    Thread Starter marthalee

    (@marthalee)

    15 years, 8 months ago

    get good at explaining why the css validation isn’t an issue

    problematic, if part of one’s selling proposition is clean, standards-compliant code… I was in process of getting good at explaining why this is better than buggy, deprecated, full-of-hacks code!

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

The topic ‘2010 css errors and warnings (validation)’ is closed to new replies.