Re: [csswg-drafts] [css-text-4] Rename `trim-auto` to `trim-both` (#10161)

The CSS Working Group just discussed ``[css-text-4] Rename `trim-auto` to `trim-both` ``, and agreed to the following:

* `RESOLVED: rename trim-auto to trim-both`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> fantasai: text-spacing has a bunch of values.<br>
&lt;TabAtkins> fantasai: as we've tweaked 'normal' and the proeprty syntax, we've gotten to a place where we have "normal" being a baseline behavior where we allow spacing at start/end of th eline, but collapse within the line<br>
&lt;TabAtkins> fantasai: And we have trim-start, trim-all, space-all, space-first<br>
&lt;fantasai> https://github.com/w3c/csswg-drafts/issues/10161#issuecomment-2033649072<br>
&lt;TabAtkins> fantasai: There's also trim-auto which is baseically trim-start + trim-end + the baseline "trim in the middle" behavior<br>
&lt;TabAtkins> fantasai: It makes sense to rename to trim-both, then<br>
&lt;TabAtkins> fantasai: Murakami-san seems to align on that<br>
&lt;TabAtkins> fantasai: I believe this is the one keyword not yet shipped by Chrome, so it should still be fixable<br>
&lt;TabAtkins> proposed resolution: rename trim-auto to trim-both<br>
&lt;TabAtkins> RESOLVED: rename trim-auto to trim-both<br>
</details>


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


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

Received on Wednesday, 10 April 2024 16:39:06 UTC