Re: [csswg-drafts] [css-fonts] Reconsider the definition of "first available font" (#4796)

The CSS Working Group just discussed `[css-fonts] Reconsider the definition of "first available font" #4796`, and agreed to the following:

* `RESOLVED: The first available font is the first font in the font-family list whose unicode includes the space glyph`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-fonts] Reconsider the definition of "first available font" #4796<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/4796<br>
&lt;dael> AmeliaBR: fantasai comment is resolution from a couple months ago was illogical so we should take it from there<br>
&lt;dael> fantasai: We rescinded the resolution in the same session b/c we had it could be 0.5 em or a glyph but fonts are neither so makes no sense. I think we start at the top.<br>
&lt;dael> Rossen_: What's the proposal?<br>
&lt;Rossen_> q<br>
&lt;dael> florian: It's okay if the first available font does not contain all glyphs. I think ch unit uses 0 glyph, ic uses a particular character. If the glyphs are missing the units can say I default to 1em or whatever. But we should still figure out what the first available font is<br>
&lt;dael> AmeliaBR: So one prop is the first font in the font stack with any valid glyphs is your first available font?<br>
&lt;dael> myles: That's what we do in WK. THe first font is the primary font and if it doesn't support the characters we'll use another one<br>
&lt;dael> florian: Problem in the spec is it says first font if it doesn't cotnain space it doesn't count<br>
&lt;dael> florian: One reason is common to put first font and reduce it via the unicode range. You're just using that font for &amp; or something and want rest of the stack for the rest.<br>
&lt;dael> florian: As jfkthame pointed out it's if the font contains. If the change to if the unicode range it's webcompat<br>
&lt;dael> dbaron: Suggestion in issue is change it to be if unicode range matches the space and than it was added what to fallback to if there's not a glyph<br>
&lt;dael> fantasai: sounds like it's what we did before is for the value of ch and than ammend algo for first available font to see if space is in its unicode range<br>
&lt;dael> florian: And for ch unit it already says that. It says in [reads] (it's 0.5em wide)<br>
&lt;dael> florian: Could be interpreted as if not in first available font<br>
&lt;fantasai> https://www.w3.org/TR/css-values-3/#ch<br>
&lt;fantasai> "In the cases where it is impossible or impractical to determine the measure of the “0” glyph, it must be assumed to be 0.5em wide by 1em tall."<br>
&lt;dael> AmeliaBR: Can someone type up a resolution text for the proposal?<br>
&lt;fantasai> "Equal to the used advance measure of the "0" (ZERO, U+0030) glyph found in the font used to render it."<br>
&lt;dael> dbaron: I don't quite understand what happened last time, though we did retract original resolution in that discussion<br>
&lt;dael> florian: b/c made no sense. We said font becomes 0.5em which makes no sense.<br>
&lt;myles> Proposed Resolution: The first available font is the first font in the font-family list whose unicode-range supports the space glyph<br>
&lt;dael> fantasai: I put in text from Values. It says ch is the advance measure of the 0 in font used to render it. WHich is not same as first available. So that's separate. Need to resolve what first available font is. If there's an issue with ch it's separate.<br>
&lt;dbaron> I think a more specific proposed resolution is to accept jfkthame's proposal at the end of https://github.com/w3c/csswg-drafts/issues/4796#issue-568427691<br>
&lt;dael> fantasai: We should take prop from myles and if there's an issue for def of ch that's sep against values and units<br>
&lt;dael> AmeliaBR: On prop resolution do we have concept in spec what unicode means for system and generic<br>
&lt;dael> myles: Assumed to have definite range of every unicode character. Spec lists it out.<br>
&lt;AmeliaBR> s/unicode/unicode-range/<br>
&lt;dael> florian: Another clarification. If the first font in stack doesn't have space we skip it. If it does do we look if it has the glyph?<br>
&lt;dael> myles: We do not<br>
&lt;dael> Rossen_: Thoughts or objections to "The first available font is the first font in the font-family list whose unicode-range supports the space glyph"<br>
&lt;AmeliaBR> s/unicode-range character/unicode character/<br>
&lt;fantasai> s/supports/includes/<br>
&lt;AmeliaBR> s/what unicode means/what unicode-range means/<br>
&lt;dael> dbaron: There was working in issue<br>
&lt;dael> jfkthame: Should be talking about character not range<br>
&lt;dael> RESOLVED: The first available font is the first font in the font-family list whose unicode includes the space glyph<br>
&lt;fantasai> s/glyph/character/<br>
&lt;fantasai> s/unicode/unicode-range/<br>
&lt;dbaron> s/working/wording/<br>
&lt;AmeliaBR> s/first font/first available/<br>
</details>


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

Received on Thursday, 7 May 2020 22:30:06 UTC