css shorthand for font, when did this become unacceptable? Options

[GTAV6]

i've always placed all my css font attributes into one shorthand entry - however... i've just discovered that doing this can now make firefox and chrome spit the dummy and default back to their own built-in standards. upon checking with w3c (something i've not bothered to do with my css for a long time), my font shorthand no longer validates as css3, claiming "Value Error : font / is not a font-family value". huh?

now, it seems, instead of using my usual font: weight style size/line-height family; i have to break it back down into five seperate entries before my css will validate - and ff & chrome play nicely again.

have i missed some new css development or something?

[strifus]

Validating your CSS in W3C is probably the reason that you are getting the error in the first place. Apparently, a bug was reported at http://lists.w3.org/Archives/Public/www-va...or-css/2012May/ giving the error you listed even if the syntax was correct. Check it out. As far as I know, there it hasnt been fixed yet.

As to why FF and Chrome would spit the dummy, I have no idea.

This post has been edited by strifus: Jul 6 2012, 09:03 PM