- From: Bramus! via GitHub <sysbot+gh@w3.org>
- Date: Mon, 30 Jan 2023 21:22:57 +0000
- To: public-css-archive@w3.org
Thanks @mirisuzanne for posting this issue. It was still on my todo, but glad to see you posted it _(in a more articulate way than I ever could)_. The idea came up after playing with the `@scope` prototype in Chrome and somewhat at the same time thinking about [sibling scopes](https://github.com/w3c/csswg-drafts/issues/7751). For sibling scopes it would seem very weird that one of the boundaries is included by default and the other not. To make sense, both boundaries should either be included, or both excluded. With _regular_ `@scope` excluding the end boundary by default, excluding the start boundary seemed like the logical thing to do in order to reach a balanced type of selection. From thereon out [`:scope`](https://w3c.github.io/csswg-drafts/selectors/#the-scope-pseudo) came to mind to target the start boundary element itself. One thing that might seem a bit weird in this scenario is that there’s only one pseudo available to select the start boundary, not one to select the lower boundary. Miriam had arguments that this wasn’t too big of a problem. -- GitHub Notification of comment by bramus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8377#issuecomment-1409359613 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 30 January 2023 21:22:59 UTC