Re: [csswg-drafts] [css-fonts] extent font-size-adjust to take a pair of values: <metric> <number> (#6160)

The CSS Working Group just discussed `[css-fonts] extent font-size-adjust to take a pair of values: <metric> <number>`, and agreed to the following:

* `RESOLVED: add new metrics that can be used to harmonize the font size of fonts used in fallback`

<details><summary>The full IRC log of that discussion</summary>
&lt;astearns> topic: [css-fonts] extent font-size-adjust to take a pair of values: &lt;metric> &lt;number><br>
&lt;astearns> github: https://github.com/w3c/csswg-drafts/issues/6160<br>
&lt;fremy> jfkthame: this was prompted by the discussion about size adjust descriptor<br>
&lt;fremy> jfkthame: we want to harmonize when we have mixtures of fonts<br>
&lt;fremy> jfkthame: font-size-adjust allows you to use the x-height of the font to size things<br>
&lt;fremy> jfkthame: this is very latin-centric however<br>
&lt;fremy> jfkthame: for exemple you might want to harmonize the ascent/descent of the font instead<br>
&lt;fremy> jfkthame: because x-height might be meaningless to my language<br>
&lt;fremy> jfkthame: this sounds like a natural extension to me, but I wanted feedback<br>
&lt;fremy> fantasai: this makes sense to me<br>
&lt;fremy> fantasai: I support the proposal<br>
&lt;fremy> florian: same<br>
&lt;fremy> florian: I would like to note that the ascent+descent combination is problematic<br>
&lt;fremy> florian: because it depends on the baseline<br>
&lt;fremy> florian: it's easier to stick to things that are distances from the baseline<br>
&lt;fremy> florian: otherwise you are adding a feature to realign<br>
&lt;fantasai> s/are/adding/need to add/<br>
&lt;fremy> jfkthame: I don't propose to adjust the alignment<br>
&lt;fremy> jfkthame: just the font size<br>
&lt;fremy> fantasai: yes, you would need to use ideographic alignement in some cases<br>
&lt;fremy> florian: ok, that sounds convincing<br>
&lt;fremy> myles: did we consider IC-height?<br>
&lt;florian> [IC = Ideographic Character]<br>
&lt;fremy> fantasai: we probably want to have logical variants of these as well<br>
&lt;fremy> myles: philosophically this proposal makes sense<br>
&lt;fremy> myles: but to change the spec, I will need a list of tokens to consider for the first argument<br>
&lt;fremy> myles: I might have some opinions on the set<br>
&lt;fremy> myles: descent doesn't seem useful for example<br>
&lt;fremy> astearns: how often do people use font-size-adjust?<br>
&lt;fremy> fantasai: it's not cross-browser so it might be lower than we think<br>
&lt;fremy> jfkthame: I found a lot more uses that I expected actually<br>
&lt;florian> s/ok, that sounds convincing/ok, that sounds convincing, you can use vertical-align to deal with any alignement problem/<br>
&lt;fremy> jfkthame: but however it often as no effect since it only applies if font don't load<br>
&lt;fremy> astearns: are we sure we don't complexify too much?<br>
&lt;fremy> fantasai: I think it's fair to support asian languages better<br>
&lt;fremy> fantasai: some languages don't even have opentype metrics, but at least this would add support for languages for which we have metrics<br>
&lt;fantasai> s/non-european/<br>
&lt;fremy> fantasai: and we have a mechanism to add new metrics if they are created later<br>
&lt;fantasai> s/asian/non-european/<br>
&lt;fremy> astearns: which browsers support this right now?<br>
&lt;fantasai> s/we have a mechanism/it provides a design which works/<br>
&lt;fremy> myles: probably just firefox?<br>
&lt;fremy> jfkthame: and behind a flag in chrome<br>
&lt;fremy> myles: and webkit would implement when we add the overrides in the font description block<br>
&lt;fremy> myles: no objection to add, we can discuss the set later<br>
&lt;fremy> astearns: sounds like we have a consensus<br>
&lt;fremy> astearns: any objection?<br>
&lt;fremy> RESOLVED: add new metrics that can be used to harmonize the font size of fonts used in fallback<br>
&lt;fremy> florian: btw we need to find a way to work with the opentype people<br>
&lt;fremy> florian: so we can provide feedback<br>
&lt;fremy> florian: I don't have a plan to propose, but maybe we can create a community group<br>
&lt;fremy> florian: maybe that is not necessary, but it would be nice to figure it out<br>
&lt;florian> s/maybe we can create a community group/there is a community group created recently/<br>
&lt;fremy> astearns: indeed, the set of metrics can be a good think to ask to the opentype people<br>
&lt;fremy> astearns: let's make sure that we don't ping them about bad fonts though<br>
&lt;florian> s/maybe that is not necessary/I don't know for sure how to engage with the fonts people/<br>
&lt;fremy> astearns: there are lots of fonts that are reporting wrong metrics<br>
&lt;fremy> astearns: and it's not the fault of the committee<br>
&lt;florian> https://github.com/w3c/font-text-cg/<br>
</details>


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


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

Received on Tuesday, 6 April 2021 14:23:00 UTC