- From: Shinyu Murakami via GitHub <sysbot+gh@w3.org>
- Date: Wed, 03 Apr 2024 06:20:25 +0000
- To: public-css-archive@w3.org
This is just an editorial suggestion related on renaming `trim-auto` to `trim-both`, I think it would be better to change the order of the value definitions from
> \<spacing-trim\> = space-all | normal | trim-both | trim-start | space-first | trim-all
to
> \<spacing-trim\> = space-all | normal | space-first | trim-start | trim-both | trim-all
(I think this is more natural: `space-first` is near `normal` and `trim-both` is near `trim-all`)
and the table of the "summary of what the various values do" would be changed to:
<table>
<thead>
<tr>
<th>Value
<th>Trim at line start
<th>Trim at line end
<th>Trim adjacent pairs
<th>Trim everywhere
<tbody>
<tr>
<th>space-all
<td colspan=4>no
<tr>
<th>normal
<td>no
<td rowspan=3>only if would not fit
<td rowspan=4>yes
<td rowspan=4>no
<tr>
<th>space-first
<td>yes except on the first line
<tr>
<th>trim-start
<td rowspan=2>yes
<tr>
<th>trim-both
<td>yes
<tr>
<th>trim-all
<td colspan=4>yes
<tr>
<th>auto
<td colspan=4>user-agent specific / platform dependent
</table>
With this table, it is much understandable that `trim-both` means trim at both line start and line end.
--
GitHub Notification of comment by MurakamiShinyu
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10161#issuecomment-2033649072 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 3 April 2024 06:20:26 UTC