- From: Florian Rivoal via GitHub <noreply@w3.org>
- Date: Wed, 01 Oct 2025 09:43:08 +0000
- To: public-css-archive@w3.org
For the button use case, I agree with @andreubotella that there are other patterns through which this is usually achieved. For the purpose of closing quotation marks, I think the pattern shown in https://github.com/w3c/csswg-drafts/issues/11253#issuecomment-2821606428 shows how this is solvable without special-casing ::after. Sure, it requires some cooperation between what sets the closing quote and what sets the ellipsis, but you'll need some anyway to even know that the `::after` is being used for a closing quote, so that seem fine. Arguably, one extension we might want, to build up on that pattern, but in a more generic way, is to allow this as a value of `block-ellipsis` instead of just `<string>`: > [ \<string\> | [\<quote\>](https://www.w3.org/TR/css-content-3/#typedef-quote) ]+ Though the behavior should be different from when it's used in the `content` property, and not change the level of nesting of the quotes, since that would be redundant with `::after`, which is hidden, but still applied. That said, while we can expand in that direction, I'm not sure I'd rush there before there's clearly established demand for this extra complexity. We can always come back to it later. So my proposal would be: * don't special case `::after` * defer to a later level the ability to use `close-quote` -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11253#issuecomment-3355537675 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 1 October 2025 09:43:09 UTC