Re: [csswg-drafts] [css-cascade] [css-nesting] Figure out whether we're fine with "shifting up" bare declarations after rules (#8738)

Fully agree with @emilio.

I _initially_ thought that we should serialize back to bare declarations for outer `cssText` since it's shorter, nicer, and basically "why not". But the round-trip issues and other edge cases convinced me the other way.

@LeaVerou You said that we should consider another name for `@nest`, would that mitigate the situation? If the name better explains what it does/is, maybe its presence will feel less offensive? `@this`? `@self`? `@wart`?

> changing APIs in ways that are confusing / inconsistent (like not returning rules from .cssRules)

Yes, let's avoid this, please. Getting creative about the OM structure is even more intrusive than getting creative about its serialization.


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


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

Received on Wednesday, 17 April 2024 08:24:29 UTC