Re: [csswg-drafts] [css-fonts] Suggest allowing a list of font-family values in @font-face (#3691)

The CSS Working Group just discussed `[css-fonts] Suggest allowing a list of font-family values in @font-face #3691`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-fonts] Suggest allowing a list of font-family values in @font-face #3691<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/3691<br>
&lt;dael> mike: I couldn't see a reason not to<br>
&lt;dael> mike: It expands to multiple fontface blocks. Not sold on need for it, but struck me as a why not. I think chris is trying to clear issues<br>
&lt;dael> myles: I think emilio brought up a problem with it.<br>
&lt;fantasai> s/emilio/Amelia/<br>
&lt;emilio> s/emilio/Amelia<br>
&lt;dael> TabAtkins: Problem is same as if you do multiple font faces still. Possibly not what author intends, but well defined what would happen<br>
&lt;dael> TabAtkins: You can define multiple faces that are identical except name<br>
&lt;dael> myles: if 2 font face blocks, one with a one with a,b should they be combined together<br>
&lt;dael> TabAtkins: SHould be exactly as if a,b was to separate faces<br>
&lt;dael> AmeliaBR: One related question si will this only apply to font family name or other descriptors<br>
&lt;dael> mike: Only intended name. Easiest to leave at that<br>
&lt;dael> AmeliaBR: I think the example of something like a black font which is sometimes referred to with black or as 900 weight generic is a good example<br>
&lt;dael> AmeliaBR: Question for me if it's sensible syntax<br>
&lt;dael> myles: mike said it's a why not instead of use case. If this is valuable you would see authors having to duplicate and I don't see it on the web<br>
&lt;dael> mike: That's there I got to as well<br>
&lt;dael> AmeliaBR: Sounds like we lean no change?<br>
&lt;dael> mike: If there's an argument against change or change sake that's it. Might be a localization argument to give fonts Japanese and English name. I'm not qualified for that.<br>
&lt;dael> florian: This is just syntaxtic sugar for repeating<br>
&lt;dael> fantasai: So unless we see that no good reason to change<br>
&lt;dael> florian: Is there acss preprocessor that does it?<br>
&lt;dael> mike: not that I know of<br>
&lt;dael> Rossen_: Than let's hold now and come back if there's use cases<br>
&lt;dael> myles: Let's close it.<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3691#issuecomment-625531294 using your GitHub account

Received on Thursday, 7 May 2020 22:35:46 UTC