Re: [csswg-drafts] [css-inline-3] Naming Stuff (#8067)

The CSS Working Group just discussed `[css-inline-3] Naming Stuff`, and agreed to the following:

* `RESOLVED: leading-trim: normal;   >>   text-box-trim: none;    AND    text-edge  >>   text-box-edge`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> fantasai: This is a long discussion about naming stuff. May come back for more naming. A number of properties in inline spec that are not most understandable. I think that the person who put this on agenda wanted leading-trim and text-edge to be taken.<br>
&lt;dael> fantasai: text-box-sizing and text-box-trim have been discussed for text-tedge and leading-trim respectively. Also rename initial values to normal<br>
&lt;dael> fantasai: i think it makes sense and we should go in this direction. Not sure we'll end up where b/c some discussion about splitting what is text-edge into two properties.<br>
&lt;dael> fantasai: text-edge -> text-box-sizing, leading-trim -> text-box-trim and initial values are normal<br>
&lt;dael> fantasai: Though text-box-trim could be none<br>
&lt;dael> jensimmons: I think leading-trim initial is normal and text-edge initial is leading. Makes a lot of sense to change that<br>
&lt;astearns> +1 to removing ‘leading’ from the list of words we use<br>
&lt;dael> jensimmons: text-box-trim is none b/c won't do any extra trimming and then you change to trim<br>
&lt;fantasai> text-box-sizing: normal | other stuff<br>
&lt;fantasai> text-box-trim: none | other stuff<br>
&lt;dael> fantasai: Makes more sense. Going with ^<br>
&lt;dael> jensimmons: Wondering a bit if txt-box-sizing makes the most sense or make sense to text-box-edge. It's really about finding top and bottom edge. Where will you trim to.<br>
&lt;dael> fantasai: And we have values for top and bottom independent, right?<br>
&lt;dael> jensimmons: I think you can use one value and it's used for both if both in other property or you can list them separately<br>
&lt;dael> jensimmons: Are you saying making that two separate properties?<br>
&lt;dael> fantasai: No, separate discussion about text-edge. Does 2 things currently, one is change how we measure an inline box to see if it fits in the line-box. Right now include text + half-leading and text-edge lets you cut that down.<br>
&lt;dael> fantasai: that's per line box. Effects how text is measured in a paragraph<br>
&lt;dael> fantasai: leading-trim we say if you trim start or end and what's top of first line box or bottom of last and that drills down through descendants. In that case we say wehre we trim to and we look at text-edge. astearns raised a question about if we should have a separate prop to let you control that perhaps defaults to text-edge<br>
&lt;dael> fantasai: I think what you're proposing is an improvement, we shouldt ake and realize we might come back<br>
&lt;fantasai> s/astearns/Alan (from Apple)/<br>
&lt;dael> jensimmons: Hearing what you desc makes me wonder having both properties used. edge when you say which edge and sizing to change calc of box height. That makes sense to me<br>
&lt;dael> fantasai: Makes sense<br>
&lt;dael> jensimmons: text-box-sizing people like because they know box-sizing. Pointing at lines is different than saying border-box. I don't know what that means for a first step.<br>
&lt;dael> jensimmons: Rename to text-box-trim and then text-box-edge for now? Or do we call it sizing for now?<br>
&lt;dael> fantasai: Let's go with what you suggested and we can come back once we dig into other issues<br>
&lt;dael> jensimmons: text-box-edge or text-box-sizing to start?<br>
&lt;dael> fantasai: I don't know. Could go either way<br>
&lt;dael> Rossen_: If we start with text-box-edge given it lets you control the 2 edge sep that would be better b/c text-box-sizing is similar to box-sizing and that applies to the whole box. text-box-sizing suggests both would be effected so prefer -edge<br>
&lt;dael> fantasai: Makes sense. And we could split into longhands eventually. text-box-edge-start makes more sense<br>
&lt;jensimmons> leading-trim: normal;   >>   text-box-trim: none;    AND    text-edge  >>   text-box-edge<br>
&lt;dael> fantasai: Don't know we'll need it but good we could go<br>
&lt;dael> jensimmons: Talking about this ^<br>
&lt;dael> jensimmons: Portential of text-box-sizing or breaking things out later<br>
&lt;tantek> +1 Rossen_'s reasoning on naming.<br>
&lt;dael> fantasai: Yeah<br>
&lt;dael> jensimmons: sgtm<br>
&lt;dael> Rossen_: Feedback or objections?<br>
&lt;dael> fantasai: Going in the right direction. Not sure it's at the finish line, but happy to make those edits<br>
&lt;dael> jensimmons: sgtm. We have an impl but behind a flag. the name changes are important to get quickly so there won't be old tutorials with wrong names<br>
&lt;dael> Rossen_: not hearing objections<br>
&lt;dael> RESOLVED: leading-trim: normal;   >>   text-box-trim: none;    AND    text-edge  >>   text-box-edge<br>
</details>


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


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

Received on Thursday, 2 March 2023 00:52:54 UTC