Re: [csswg-drafts] [css-cascade-6] Scoped selectors shouldn't match the scope root unless explicitly requested with :scope? (#8377)

That makes sense, yes. 

For matching semantics with `&` in a scoping context, I see a couple options:

1. Scoped `&` is identical to `:scope`, and only matches the root element. It makes the selector _scope-containing_, and `& &` wouldn't match anything. 
2. Scoped `&` refers to the scoping root selector, rather than the scoped element itself. That allows `& &` to be resolved as per usual, but then either:
    a. It continues to make the selector scope-containing, so there is no implied ancestor `:scope`
    b. It is not scope-containing, so a bare `&` would be treated as `:scope &`
3. Revert the pervious decision, and don't allow `&` directly in `@scope`

Laying out those options, I think 2a is the one that would match expectations most accurately.

-- 
GitHub Notification of comment by mirisuzanne
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8377#issuecomment-1433608335 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 16 February 2023 19:32:44 UTC