Re: [csswg-drafts] [css-inline-3] inline boxes and line-fit-edge vs text-box-trim/edge (#10834)

The CSS Working Group just discussed `[css-inline-3] inline boxes and line-fit-edge vs text-box-trim/edge`.

<details><summary>The full IRC log of that discussion</summary>
&lt;bramus> fantasai: Was making the edits for this and noticed we have an issue around<br>
&lt;bramus> … resolution wasnt 100% clear.<br>
&lt;bramus> … have two different line height sizing modes<br>
&lt;bramus> … depending on line fit<br>
&lt;bramus> … we resolveed to make t-b-trim affect inline boxes<br>
&lt;bramus> … and it definitely affects where the content edge is drawn<br>
&lt;noamr> fantasai: we have a transparency principle<br>
&lt;noamr> fantasai: an unstyled span around some text should not affect layout<br>
&lt;fantasai> So, for example, &lt;em>Some text&lt;/em> and &lt;em>&lt;span>Some text&lt;/span>&lt;/em> must have identical rendering, no matter what styles are applied to &lt;em>.<br>
&lt;noamr> Sorry, have to drop<br>
&lt;fantasai> Proposal Part A: When line-fit-edge is normal, we ignore the margin/border/padding and just use the line-height for sizing. In this case, text-box-trim changes the content edge (affecting backgrounds and borders), but does not change the height contribution of the inline (which continues to be based on line-height).<br>
&lt;JakeA> Thank you all! Have a good break<br>
</details>


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


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

Received on Wednesday, 18 December 2024 18:03:49 UTC