New rules for CSS validation?!

no. never had that. only really weird thing happend to me by playing around wit the doctype. i guess it’s your document type (maybe changed recently?).

did you validate by refer, upload or copy/paste? if some new plugin added inline css to your site it might be that css code and not the theme-css (blix).

a url to your css and preferbly your website would help.

thata€?s the point I havena€?t changed anything, and did not edit the css file either, no new plugins for the last 2 months, and Ia€?m using wordpress’ default text editor.

I have had this problem too. In the past few days my site has gone from valid with one error to valid with, like, 45 errors, and I haven’t changed a thing.

BTW Mentor, have you cheked this https://jigsaw.w3.org/css-validator/validator?uri=https://www.m3nt0r.de/blog/ ?

yes, but cant be bothered to fix, heh. ^^ this gettin outta hand. but i have no problems with any browser, so i’m happy. the -moz stuff is of course a css hack, and hacks are never valid, but if i want my page to look like it does theres no way around.. or maybe is. dunno. im happy with the page actually, but thanks for the input. in some silent moment i will try to fix them all ?? at least the xhtml is valid and that counts most to me. took me some time to make all plugins valid.

Something has definitely changed. Mine was fine no more than a week ago and now it’s telling me I need a background color for every little thing. Pfft.

true. i was wondering about the validation result of mine too. wants a color everywhere.. thats not smart in my eyes. i dont see the problem why color attributes cant be inherit (as they was?). relative items should normally (as they still do) adopt the background-color property.

thats right, but even more – mine was absolutely fine a few DAYS ago, still xhtml valid, no problems with rss, but css says the same thing – background color and 2 errors that are not really errors, as far as know css my .css is perfectly fine. Thus, WTH?

about that background/foreground color thing:

Thats a pure notice. The validator cannot know if the css would be valid combined with the structure of document (thus the mentioned items get their (missing) background and color attributes from styled parent items).

in plain css, it looks wrong to the validator. in action (live) it’s all o.k. i think this can be safely ignored.

Edit: you can stop him warning by adding “background-color: transparent;” to all elements named.

Edit2: this idea on how to stop the warnings: its not 100% save.. it depends on how your document is made. also you will loose redundancy. imagine the needed effort if you wanna change colors later… i go for ignoring..

well, maybe it’s a problem on there side? Whats the reason for this change?

Heh, this is crazy https://jigsaw.w3.org/css-validator/validator?uri=http%3A%2F%2Fwww.ads-software.com%2Fdevelopment%2F&usermedium=all wth are they doing? Whats the reason to use their stupid validator if there is no website on the net that would be valid by such means. Mist.

I’ve recently done a theme, and do not have a background color declared for everything and it validates just fine.

Main thing I see is it’s not accepting the -moz-radius attributes.

mine has 2 errors with
Invalid number : line-height Parse Error – [empty string]

looks like no one cares about the new rules. I’ve deleted the link to css validation from my site, and now Ia€?m happy heh

Just don’t validate for all warnings, only: most important.

Regards,

Karel

Well, it should be noted a ‘warning’ is not an error. It’s just telling you that strictly speaking, you aren’t following the defined rules of CSS – i.e. defining color and background-color.