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

So the proposal is basically "`@nest`, but without parsing or serializing the prelude ever", if I'm understanding it correctly?

I mean, I still think that parsing and serializing _a rule_ is strictly better and more consistent, but if this is the only think WebKit is blocking on, then I guess I can live with it... We can always change course if people hit issues with `.insertRule` and serialization and such.

For example, it's very weird that you'd call `.insertRule` / `.insertDeclarations`, and that'd make stuff serialize to something like:

```
padding-top: 10px !important;
padding-top: 10px;
```

Which is something that otherwise would get simplified at parse time.

Serializing to something that explains what's going on like:

```
@nest { padding-top: 10px !important }
@nest { padding-top: 10px }
```

Seems a lot better to me. But I don't think it necessarily introduces any correctness issues other than that...

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


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

Received on Tuesday, 21 May 2024 13:22:18 UTC