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

@fantasai's proposal looks acceptable to me, although including the "leading" declaration list in `cssRules` is problematic, as it requires a new use-counter and waiting many months for good data.

> It serializes as a raw declaration list.

That means it won't round-trip "structurally", like we talked about before. But maybe that's not so bad.

> We would also be OK with alternative solutions that don't introduce an at-rule, such as [...] including only interleaved declaration lists in .cssRules.

In that case, I suggest that we resolve on the proposal, minus the change to `cssRules` for now. "Making [cssRules] a comprehensive and consistent representation of all the contents of the style rule" does makes sense to me, but it would be nice if we could consider this _separately_ in order to deal with the most urgent part ASAP.

> Extend .insertRule() to parse declarations (or add .insertDeclarations())

It makes sense, but actually we could do this separately as well?

-- 
GitHub Notification of comment by andruud
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10234#issuecomment-2122146046 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 09:09:27 UTC