Re: [csswg-drafts] [css-syntax][css-nesting] Design of `@nest` rule (#10234)

> Especially since making this rule useful seems like the only path forward with such strong objections from both sides.

But we also have to be careful with that.
If it always has an effect then it can't be used to solve the problem at hand and we end up where we started.

This rule must be a noop in its simplest form.

-------

I really like @mirisuzanne suggestion because it has no effect when there is no prelude.
There is a lot of stuff to consider but also a lot of potential.

Some unstructured questions that spring to mind:
- Should its effects be limited to `<dashed-ident>`'s (and maybe `<custom-ident>`)? ie. any regular declaration would remain untouched.
- Could it prefix all `<custom-ident>`'s and `<dashed-ident>`'s? Also for things like `@keyframes`? How badly does it break things like grid template area's?
- Could you import a stylesheet and apply grouping to its contents? Essentially ensuring that there aren't any naming conflicts when mixing 3rd party stylesheets.

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


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

Received on Friday, 26 April 2024 17:37:04 UTC