- From: Myles C. Maxfield via GitHub <sysbot+gh@w3.org>
- Date: Thu, 11 May 2023 20:18:42 +0000
- To: public-css-archive@w3.org
litherum has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-inline-3] It's impossible to use `text-box-trim` without changing line progression within the paragraph == https://drafts.csswg.org/css-inline-3/#leading-trim > Name: | text-box-trim > -- | -- > Value: | `none \| start \| end \| both` > > ... > start > For [block containers](https://drafts.csswg.org/css-display-4/#block-container): trim the [block-start](https://drafts.csswg.org/css-writing-modes-4/#block-start) side of the [first formatted line](https://drafts.csswg.org/css-pseudo-4/#first-formatted-line) to the corresponding [text-box-edge](https://drafts.csswg.org/css-inline-3/#propdef-text-box-edge) metric of its [root inline box](https://drafts.csswg.org/css-inline-3/#root-inline-box). The two properties `text-box-trim` and `text-box-edge` have very different purposes. One changes the spatial relationship of blocks with respect to each other, whereas the other changes the progression of lines within a block. At a fundamental level, these purposes are orthogonal. If an author _just_ wants to change their blocks' positions, they shouldn't have to change the progression of lines _within_ their blocks. Philosophically, there is no reason to connect `text-box-trim` and `text-box-edge` the way they're linked in the spec now. Instead, we'd like to propose changing the grammar to be something like (cribbed from the `text-box-edge` property): > Name: | text-box-trim > -- | -- > Value: | `leading \| [ text \| cap \| ex \| ideographic \| ideographic-ink ] [ text \| alphabetic \| ideographic \| ideographic-ink ]?` This would allow `text-box-trim` and `text-box-edge`'s behavior to be orthogonal to each other. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8829 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 11 May 2023 20:18:44 UTC