- From: jfkthame via GitHub <sysbot+gh@w3.org>
- Date: Mon, 29 Aug 2022 18:56:19 +0000
- To: public-css-archive@w3.org
> It would, but (unless there is a later, duplicate, valid) font-family descriptor then the at-rule doesn't apply to anything. True; but as currently written, a font-family descriptor with a syntax error (such as a generic name) would cause the entire rule to be dropped, *even if* there's a subsequent, valid font-family descriptor. (Which is not how any existing implementation behaves, AFAICT.) What about a rule with no font-family descriptor at all? The text currently says: > [@font-palette-values](https://drafts.csswg.org/css-fonts/#at-ruledef-font-palette-values) rules require a [font-family](https://drafts.csswg.org/css-fonts/#descdef-font-palette-values-font-family) descriptor; if it is missing, the @font-palette-values rule is invalid and must be ignored entirely. Does this mean that the rule should be dropped at parse time, and not appear in the OM, or it it simply telling us that the rule will not apply to anything and therefore "must be ignored entirely"? (Existing implementations appear to accept a rule that lacks font-family, and https://github.com/web-platform-tests/wpt/blob/master/css/css-fonts/parsing/font-palette-values-valid.html thinks they're valid even though they're pointless. Is that the intention, or are the implementations and the testcase incorrect?) -- GitHub Notification of comment by jfkthame Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6916#issuecomment-1230725321 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 29 August 2022 18:56:21 UTC