Rune Lillesveen

@tabatkins Emilio left a question for you whether the specs snapshotting state should be called out explicitly in the cssom-view spec, which is relevant for this review: https://github.com/w3c/csswg-drafts/pull/11037#discussion_r1801511393

I don't think we made a conscious choice here, but the width/height of the container in CSS pixels as seen by the container just follows from the implementation.

> * When we have a non-default root overflow specified, it should absolutely propagate to the viewport. This is certainly a browser bug (in all browsers). I'm pretty sure the...

> > I think `blocked by a modal dialog` should be defined in terms of `interactivity` (either set as a presentational hint on the root, or using an UA stylesheet...

I think it will be hard to support `@mixin`s with selectors inside the `@mixin`. Selectors are typically matched from right to left in impls and would be started inside the...

> I always saw `@mixins` more like syntactic sugar. > > Where resolving would be roughly equivalent to wrapping in `&{}` and inserting that where `@apply` used to be. >...

> @lilles Some follow-up about nesting in mixins… I don't think that constraint would be a blocker for making this a useful feature. I'm curious if there's any useful distinction...

> > > Mixins return [...] rule blocks (including selectors and other at-rules) > > > [...] mixins [...] would be resolved during variable substitution > > > > >...

> I'm sorry, Rune, but I don't understand what connection your reply has to what I said. Could you elaborate? I suspect one or both of us is misunderstanding what...