@bramus Is there somewhere I can follow along with...

@bramus Is there somewhere I can follow along with that? is CSSNestedDeclarations solely for that declaration-after-other-nesting situation?

That specificity attribute, is that a you-think or is that also coming natively?

Like 7 October at 14:03 | Wall-to-wall | Open on mastodon.social

3 comments

Bramus

@Kilian Awaiting the blog post I am currently finishing, you can check the spec [^1] which has some info boxes on why you need `CSSNestedDeclarations`.

Mainly to fix the shifting up behavior but also some other side-effects from before.

I manually added the `specificity` and `resolvedSelectorText` attributes for demonstration purposes. Added a note in the demo itself to clarify that.

[^1]: https://drafts.csswg.org/css-nesting/#nested-declarations-rule

7 October at 14:11 | Open on front-end.social

Kilian Valkhof

@bramus if you ever make a CSSWG proposal for that you have my +1 ;)

7 October at 14:14 | Open on mastodon.social

Kilian Valkhof

@bramus I like this solution a lot, but as a devtools builder it's annoying the number of in-flight revisions nesting is getting ;)

7 October at 14:27 | Open on mastodon.social