Re: [csswg-drafts] [css-values] ch units shouldn’t cause font downloads (#3135)

The CSS Working Group just discussed `ch units shouldn't cause font downloads`, and agreed to the following:

* `RESOLVED: ch units can cause a font download, no change to spec`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: ch units shouldn't cause font downloads<br>
&lt;fantasai> github: https://github.com/w3c/csswg-drafts/issues/3135<br>
&lt;astearns> zakim, start meeting<br>
&lt;Zakim> RRSAgent, make logs Public<br>
&lt;RRSAgent> I have made the request, Zakim<br>
&lt;Zakim> Meeting: Cascading Style Sheets (CSS) Working Group Teleconference<br>
&lt;fantasai> Scribenick: fantasai<br>
&lt;fantasai> astearns: We discussed this issue in NYC<br>
&lt;fantasai> astearns: whether ch units should cause font downloads<br>
&lt;fantasai> astearns: didn't resolve because Myles wasn't there<br>
&lt;fantasai> astearns: but general consensus was that we would leave spec unchanged, meaning ch units can cause font downloads<br>
&lt;fantasai> myles: Given the author's perspective here, they just want to make something e.g. 5ch wide, and the specific char isn't super important<br>
&lt;fantasai> myles: so if your font doesn't have the char, search down the list, but characters that are used are in the font<br>
&lt;fantasai> myles: in order to be exactly conformant you have to download things that are unnecessary<br>
&lt;fantasai> myles: They asked for ch, didn't say you have to match zero<br>
&lt;fantasai> myles: just said "make it 5 characters wide" so I think it's the wrong decision<br>
&lt;fantasai> dbaron: Idk how closely you read minutes from last time, we did talk through the various possibilities<br>
&lt;fantasai> dbaron: one of the issues was, if the ch unit doesn't trigger a font download, then you either end up in a situation where ch unit might change later<br>
&lt;fantasai> dbaron: or that it might be different whether or not downloaded a font<br>
&lt;fantasai> dbaron: other options all have problems, too<br>
&lt;fantasai> dbaron: so leaving as-is seemed like the least bad thing<br>
&lt;florian> +1 to david<br>
&lt;fantasai> +1<br>
&lt;fantasai> astearns: anyone else?<br>
&lt;fantasai> astearns: To close off, would like to resolve that we are making no change for this issue.<br>
&lt;fantasai> RESOLVED: ch units can cause a font download, no change to spec<br>
&lt;fantasai> astearns: Any other details discussed not in the spec that we should add in?<br>
&lt;fantasai> astearns: dbaron, you had a summary<br>
&lt;fantasai> dbaron: I have summarized discussion, leave to editors whether any non-normative changes needed to clarify<br>
</details>


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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 16 September 2022 16:10:32 UTC