Re: [csswg-drafts] [css-fonts-5] Computed value for font-size-adjust (#10292)

The CSS Working Group just discussed `[css-fonts-5] Computed value for font-size-adjust`, and agreed to the following:

* `RESOLVED: Close, no change`

<details><summary>The full IRC log of that discussion</summary>
&lt;emeyer> ChrisL: This is basically, do we leak values from the front font, or do we give the specified value back<br>
&lt;emeyer> dbaron: I find jfkthame's argument about inheritance to be pretty convincing<br>
&lt;astearns> s/front font/from-font/<br>
&lt;emeyer> …One of the important things about setting a font size that you're trying to do it across a region, so it makes sense that you'd want the font adjustment to apply across that same region<br>
&lt;emeyer> ChrisL: I suggest we just agree with jfkthame<br>
&lt;jfkthame> +1 :)<br>
&lt;emeyer> fantasai: I think the most you could do is to not tell the value<br>
&lt;emeyer> …You'd get information it was from-font, but it wouldn't' round trip the behavior<br>
&lt;fantasai> s/tell the value/tell the value in getComputedStyle()/<br>
&lt;emeyer> astearns: Are you saying not to agree with jfkthame?<br>
&lt;emeyer> fantasai: No, I agree, but I think the only way we could address leakage is to compute it<br>
&lt;fantasai> s/is to compute it/is to return a value from getComputedStyle() that wouldn't round trip/<br>
&lt;emeyer> dbaron: My intuition is we aren't leaking anything we don't leak in five other ways, unless someone comes up with counter examples<br>
&lt;emeyer> astearns: So we close no change, and wait for people to prove that wrong?<br>
&lt;emeyer> RESOLVED: Close, no change<br>
</details>


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


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

Received on Wednesday, 12 June 2024 15:12:52 UTC