- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Tue, 26 Sep 2023 09:56:43 +0000
- To: public-css-archive@w3.org
cdoublev has just created a new issue for https://github.com/w3c/csswg-drafts:
== [css-fonts-4] Setting `CSSFontFeatureValues.fontFamily` with invalid `<family-name>` ==
`@font-feature-values serif {}` is invalid in Chrome and FF (because `serif` is a generic font name) but Chrome accepts `CSSFontFeatureValuesRule.fontFamily = 'serif'`. FF does not yet support the attribute.
There is no procedure defined for [`CSSFontFeatureValues.fontFamily`](https://drafts.csswg.org/css-fonts-4/#dom-cssfontfeaturevaluesrule-fontfamily).
> **`fontFamily` of type `CSSOMString`**: The list of one or more font families for which a given set of feature values is defined.
But I also wonder why the attribute is not read-only, actually. What is supposed to happen if you declare the feature values in your stylesheet with a valid font family name, and then update it via CSSOM? Should the feature values be disabled?
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9412 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 26 September 2023 09:56:45 UTC