Re: [csswg-drafts] [css-inline-3] leading-trim accumulation (#5426)

The CSS Working Group just discussed `[css-inline-3] leading-trim accumulation`.

<details><summary>The full IRC log of that discussion</summary>
&lt;ntim> fantasai: leading-trim can drill through elements, if you set it on the div, it will affect the paragraph in the div<br>
&lt;ntim> fantasai: however, if the both the paragraph and div say leading-trim: trim with different metrics, then we might want to look at the closest metric<br>
&lt;ntim> fantasai: we might something similar to page-break: auto, where we can break or not break<br>
&lt;ntim> fantasai: we could add an auto value to text-box-trim<br>
&lt;fantasai> where auto means, do whatever your parent says<br>
&lt;astearns> q+<br>
&lt;miriam> ack dbaron<br>
&lt;ntim> dbaron: just to restate the question: the choice between the metric from the closest ancestor, or the metric that is determine the most amount of<br>
&lt;ntim> myles: this reminds me of text-decoration where we can never remove them<br>
&lt;miriam> ack astearns<br>
&lt;dbaron> s/is determine the most amount of/takes the largest amount off/<br>
&lt;ntim> astearns: the proposal sounds ok in theory, but I want  to see the proposal fleshed out and try some examples myself before fulling signing off<br>
&lt;ntim> astearns: this kind of sounds like trim collapsing<br>
&lt;ntim> ...and you want to avoid it<br>
&lt;ntim> florian: aren't we narrowing down to collapsing from the closest ancestor?<br>
&lt;florian> s/down to collapsing/down to trimming/<br>
&lt;ntim> astearns: Is this discussion enough to come up with a concrete proposal to evaluate?<br>
&lt;hober> scribe: myles<br>
&lt;myles> florian: it seems to me that we have a clear feeling that the largest metric is not what we want. Between the other options, we didn't discuss clearly.<br>
&lt;myles> astearns: dbaron originally asked "do you have a preference"?<br>
&lt;astearns> s/"/so /<br>
&lt;myles> dbaron: I don't have a preference. I don't understand what the issue is. I think it's closely tied to the syntax which I don't have in my head rn<br>
&lt;astearns> s/"?/?/<br>
&lt;fantasai> The three options were: take the closest metric where metric is available, take metric from closest that asks for trimming, take metric with largets amount of trimming<br>
&lt;fantasai> And I guess another one would be "outermost" metric<br>
&lt;astearns> no to the third<br>
&lt;myles> myles: how do we make progress here?<br>
&lt;myles> fantasai: astearns can help with examples, but we'll write a draft and be more specific<br>
&lt;myles> astearns: that sounds good<br>
&lt;myles> fantasai: ok<br>
</details>


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


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

Received on Friday, 15 September 2023 10:04:03 UTC