942 2004-11-15 22:58:40 +0000 Incorrect / inconsistent parsing of 'font' property 2005-08-26 14:29:39 +0000 1 1 1 Unclassified CSSValidator CSS 2.0 CSS Validator Other other RESOLVED FIXED http://www.employees.org/~lanzo/css/validator-test1.html P2 normal --- 1 lanzo ot www-validator-cvs oldest_to_newest 2622 0 lanzo 2004-11-15 22:58:40 +0000 The validator reports a warning "font-family: You are encouraged to offer a generic family as a last alternative" despite the fact that you have used a generic family in every font specification. As a test, I ran the validator across a document whose *entire* CSS content consisted solely of: <style type="text/css"> body { font: 10pt Helvetica, sans-serif normal; } </style> Even this produces the warning. Note: this matches bug 818, which for some reason was closed as "invalid" even though it is apparently quite valid and easy to reproduce. 2623 1 ot 2004-11-15 23:25:35 +0000 As far as I can tell from http://www.w3.org/TR/CSS21/fonts.html#font-shorthand the "font" shorthand does not allow to use the variant after the font-family. Hence font: 10pt Helvetica, sans-serif normal; is being parsed as if "sans-serif normal" were a font-family, which is *not* a generic family. 2632 2 lanzo 2004-11-16 15:38:22 +0000 Reason for closing bug are invalid. Tried to send details, but the email reply address is not working. Please supply valid email address so I can pass that info along. 2633 3 ot 2004-11-16 18:17:35 +0000 Re: Comment #2: if it's not possible to follow-up on this bug directly on the bug tracking system (which would be preferred, for consistency), an alternative is the (public) mailinglist for the CSS validator - www-validator-css@w3.org 2634 4 bjoern 2004-11-17 12:12:47 +0000 FWIW, I agree with Olivier. 2635 5 ot 2004-11-17 12:21:17 +0000 Initial reporter Mark sent me other examples... While the generic font-family parsing issue is not altogether clear, it appears that the parsing of the font shorthand property is sometimes wrong, and often inconsistent. I am changing the title of this bug from: Warns to use generic font-family despite having done so to incorrect / inconsistent parsing of 'font' property and raising priority/severity accordingly. For reports specifically related to the font-family property, its parsing and the warning about generic font-family, we still have bug #818. Mark, could you send your examples here, or is it OK if I do it? 2636 6 bjoern 2004-11-17 12:40:25 +0000 FWIW, I think 'font' parsing is known to be broken... 5511 7 ylafon 2005-08-26 14:29:39 +0000 Fixed, see http://qa-dev.w3.org:8001/css-validator/