- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Wed, 07 Sep 2022 22:02:18 +0000
- To: public-css-archive@w3.org
I'd like to bring this back for a proposed resolution on the following: - The default behavior is for lower boundaries to be excluded from scope - We will provide `inclusive` and `exclusive` keywords in the `@scope` syntax - The keyword comes after the selectors Depending on the resolution of #7709, the selector scoping notation may become irrelevant, or it can be handled manually as shown by @DarkWiiPlayer in the previous comment. I don't believe this should be blocked because we can't think of a shorthand for something that's already possible in a syntax we're not even sure we need. -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6577#issuecomment-1239950602 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 7 September 2022 22:02:20 UTC