- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 15 Oct 2025 16:17:59 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``[css-text-decor-4] Consider renaming `text-decoration-trim` ``, and agreed to the following:
* `RESOLVED: text-decoration-trim/column-rule-outset/row-rule-outset will be renamed to all match.`
<details><summary>The full IRC log of that discussion</summary>
<fantasai> SebastianZ: opened issue on what to call this property, unsure of the current name<br>
<fantasai> SebastianZ: wanted to decide which to take<br>
<fantasai> SebastianZ: personally, I don't think -trip or `-clip would be a good naming because that property can also extend the decoration lines<br>
<kbabbitt> s/trip/trim/<br>
<fantasai> SebastianZ: they sound like they're cutting off<br>
<miriam> q+<br>
<fantasai> astearns: I see people already voting, can we choose the winner?<br>
<astearns> ack miriam<br>
<fantasai> miriam: Pushing towards current winner, I liked the argument that we more consistently use inset/outset depending on what we consider the default, and we use consistently across properties<br>
<emilio> scribe+<br>
<emilio> fantasai: I feel strongly that if we're taking a name we should take it for column rules<br>
<emilio> ... because text-decoration-{limit,trim} implies column-rule-{limit,trim}<br>
<emilio> ... so we should clarify that if we're renaming all three of the properties, we should rename column-rules too<br>
<emilio> ... for the current name of the rules (outset) is not on the poll<br>
<kbabbitt> q+<br>
<astearns> ack kbabbitt<br>
<emilio> ... I think for the same operation they should have the same name<br>
<emilio> ... I think we use inset for a lot of layout-related stuff, to do like positioning<br>
<astearns> ack kbabbitt<br>
<emilio> ... feels weird for inset here to be about trimming a line<br>
<emilio> ... so I'd prefer a different name<br>
<fantasai> kbabbitt: wrt inset vs outset, I currently do have outset in gap decorations spec<br>
<jfkthame> q+<br>
<fantasai> kbabbitt: discussion in that issue, considering to switch to inset because I think more intuitive for authors<br>
<fantasai> kbabbitt: For this property I think inset would make more sense than outset if shrinking is more common<br>
<astearns> ack fantasai<br>
<emilio> q+<br>
<kbabbitt> gap decoration inset vs outset: https://github.com/w3c/csswg-drafts/issues/12848<br>
<astearns> ack jfkthame<br>
<fantasai> jfkthame: I thought Elika's remark about 'inset' being something we use for layout features was quite insightful<br>
<fantasai> jfkthame: This is specifically something that doesn't affect layout, purely visual rendering effect<br>
<fantasai> jfkthame: That strengthens my inclination to use a different name<br>
<fantasai> jfkthame: I'm comfortable staying with -trim. A negative amount of trim is reasonable to me<br>
<fantasai> astearns: wrt Elika's point about matching, does it make sense to use -trim for the gap case?<br>
<fantasai> jfkthame: I think it works equally well there, yes<br>
<astearns> ack emilio<br>
<fantasai> emilio: I don't have a preferred suggestion other than I agree that 'inset' is not great.<br>
<fantasai> emilio: in particular with text-decorations as well, I could imagine an author expecting '-inset' to adjust the position of the underline rather than trimming it<br>
<fantasai> emilio: Trimming makes it clear in which axis you're shrinking or growing<br>
<fantasai> emilio: while insetting might not<br>
<astearns> ack fantasai<br>
<emilio> fantasai: I agree with emilio, that was my first impression<br>
<bradk> +1 Emilio<br>
<davidleininger> +1<br>
<emilio> ... is that how we set the position of an underline?<br>
<emilio> ... I think we have -offset for that<br>
<emilio> ... so I think that's a strong consideration<br>
<emilio> ... I don't know we need to think about the most common op<br>
<emilio> ... but what's the best word for the operation<br>
<emilio> ... and then choose the sign for that<br>
<emilio> ... I don't think authors will have trouble adapting to positive / negative values<br>
<fantasai> s/trouble/no trouble<br>
<fantasai> ... the main thing is making sure the effect is clear when you read a property declaration<br>
<fantasai> astearns: Any other comments?<br>
<fantasai> SebastianZ: Naming is obviously hard!<br>
<fantasai> astearns: We could continue discussing. While -inset is highest in the poll so far, there are objections to it<br>
<fantasai> astearns: There are some opinions to stay with trim, other opinions to not, not consensus yet<br>
<astearns> ack fantasai<br>
<emilio> fantasai: would like to resolve that this property and column-rules match<br>
<emilio> ... that we resolve them as a set<br>
<miriam> +1. And if we're going to poll, I think we need to clarify what all properties are being named.<br>
<fantasai> fantasai: Propose that we resolve to rename text-decoration-, column-rule-, and row-rule- as a set<br>
<fantasai> +1 miriam<br>
<fantasai> SebastianZ: Jonathan mentiont thinking that inset/outset is related to elements while the decoration and lines are styling other than based on elements or containers...<br>
<bradk> *-lengthen: -1px<br>
<fantasai> astearns: So proposed resolution is that text-decoration/column-rule/row-rule adjustments will use the same term in the property name<br>
<fantasai> RESOLVED: text-decoration-trim/column-rule-outset/row-rule-outset will be renamed to all match.<br>
<emilio> fantasai: SebastianZ I think we need a new poll and to mark your previous comment as hidden somehow<br>
</details>
--
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8402#issuecomment-3407283833 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 15 October 2025 16:18:00 UTC