- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 07 Aug 2024 23:33:15 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-inline-3] Naming text-box-trim et al.`, and agreed to the following: * `RESOLVED: name of properties are text-box-edge and text-box-trim` * `RESOLVED: Use trim-start and trim-end instead of start and end` * `RESOLVED: the value "trim-both" for property "text-box"` * `RESOLVED: "text-box" shorthand with value "normal" set the longhands default` * `RESOLVED: Republish as WD` <details><summary>The full IRC log of that discussion</summary> <matthieud> fantasai: we took resolution to split text-box-edge<br> <matthieud> fantasai: one for line box sizing, one for triming block container<br> <matthieud> fantasai: we need to discuss some details about the syntax, the names of the properties, names of the values<br> <matthieud> fantasai: there is a new property line-fit-edge which inherits<br> <matthieud> fantasai: and also text-box-edge not inherited initial value auto which compute to the value of the line-fit-edge<br> <matthieud> fantasai: and shorthands for them together<br> <matthieud> fantasai: with a "normal" keyword for the shorthand which compute to "none" and "auto"<br> <astearns> seems OK to me, no better idea for line-fit-edge<br> <matthieud> florian: which part is resolved and which part is your invention ?<br> <matthieud> no resolved name for line-fit-edge, no resolved on the new keyword, no discussion for the shorthand text-box syntax<br> <matthieud> fantasai: no resolved name for line-fit-edge, no resolved on the new keyword, no discussion for the shorthand text-box syntax<br> <chrishtr> Koji from my team reviewed and thought it was fine, so good from Chrome's POV<br> <ntim> lgtm for the whole proposal<br> <matthieud> chrishtr: names of properties are fine<br> <matthieud> chrishtr: line-fit-edge details might need more discussion about behavior<br> <matthieud> Rossen4: we can resolve on the names ?<br> <ntim> I think these are already resolved on<br> <matthieud> RESOLVED: name of properties are text-box-edge and text-box-trim<br> <matthieud> fantasai: the shorthand is text-box but for the values there is a new normal keyword but the rest is weird like text-box-start ... etc<br> <matthieud> fantasai: maybe we should rename some values to add trim-start trim-end trim-both<br> <matthieud> fantasai: would be consistent with text-spacing<br> <matthieud> fantasai: or maybe trim instead of trim-both<br> <matthieud> florian: seems a bit hard to understand how they relate, so in favor of those changes<br> <fantasai> text-box: normal | <'text-box-trim'> || <'text-box-edge'><br> <fantasai> but text-box: start (e.g.) is pretty weird, so suggest text-box: trim-start<br> <fantasai> Precedent: text-spacing: space-all | normal | space-first | trim-start | trim-both | trim-all<br> <ntim> trim is ambiguous whether it's trim-both or trim-all<br> <matthieud> Rossen4: what is the difference between trim-both and trim-all<br> <matthieud> fantasai: trim-all trim all characters, trim-both only trim only the start edge and end edge<br> <matthieud> florian: the important is that stuff that trim is prefixed by trim-*<br> <matthieud> florian: in the text-box case the difference between both and all doesnt exist so they have the same behavior<br> <matthieud> florian: so "trim" makes sense in the text-box case<br> <matthieud> fantasai: trim and trim-both makes sense, do we want to make the keyword shorter or not<br> <fantasai> s/makes sense/both make sense/<br> <fantasai> s/or not/or compatible with text-spacing/<br> <TabAtkins> I think the `trim-*` names sound reasonable, pesonally<br> <fantasai> sure, but between `trim` and `trim-both`?<br> <TabAtkins> Ah, trim-both, if it's less than trim-all<br> <fantasai> OK. But for text-box there's no trim-all in this case, just in text-spacing<br> <TabAtkins> Sure, but consistency is good across the props<br> <fantasai> RESOLVED: Use trim-start and trim-end instead of start and end<br> <fantasai> POLL: text-box: trim; or text-box: trim-both;<br> <ntim> B<br> <astearns> b<br> <kbabbitt> B<br> <florian> 0 (ok either way)<br> <TabAtkins> b<br> <schenney> B<br> <fantasai> (clear property is clear: none | left | right | both)<br> <Rossen4> B<br> <fantasai> 0<br> <miriam> 0<br> <ChrisL> abstain<br> <matthieud> 0<br> <fantasai> kojiishii: A<br> <ntim> We should resolve on the fact the `text-box` exists as a shorthand fwiw<br> <matthieud> RESOLVED: the value "trim-both" for property "text-box"<br> <fantasai> s/text-box/text-box-trim/<br> <matthieud> fantasai: the initial value of text-box-edge is auto, but text-box-trim is none. What would be the one for text-box ?<br> <florian> +1 to the name and to the normal keyword<br> <astearns> +1 to what florian +1ed<br> <matthieud> PROPOSED RESOLUTION: "text-box" shorthand with value "normal" set the longhands default<br> <ntim> +1<br> <fantasai> s/What would be the one for text-box ?/That leaves 'text-box: none' or 'text-box: auto' for setting the initial value, and both of these read very weirdly, so I added a normal keyword to the shorthand/<br> <matthieud> RESOLVED: "text-box" shorthand with value "normal" set the longhands default<br> <fantasai> https://drafts.csswg.org/css-inline-3/#changes<br> <matthieud> fantasai: I will republish the working draft<br> <fantasai> RESOLVED: Republish as WD<br> <matthieud> TabAtkins: don't have anything ready for republication<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10675#issuecomment-2274517610 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 7 August 2024 23:33:16 UTC