- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 Dec 2023 03:14:10 +0000
- To: public-css-archive@w3.org
I suspect that @chrishtr is right, and that a value that combines the `space-start` and `trim-adjacent` behavior is the best we can get among things that don't break compat. I'm less sure about the end-of-line side of things. One of the things we've been trying to do here is to avoid exposing all the theoretical combinations when there's not use-case nor demand for them, and stick with a more limited set of keywords that only expose those combiantions that are genuinely useful. For this `space-start`+`trim-adjacent` variant, what do we want to do on the end side? Chris suggests that the initial value should combine that with `allow-end`. Do we even need any of the other possibilities? If not, the name `trim-adjacent` could just imply both the `space-start` and `allow-end` behavior, and all we have to do is add that value and make it the initial one. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9511#issuecomment-1853200737 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 13 December 2023 03:14:12 UTC