Rune Lillesveen

Tree-scoped names generally capture the tree-scope of the element where the property is specified, so if it's inherited it is still associated with the tree-scope of the element it is...

I find it a bit hard to wrap my head around the inheritance part since both ends can be inherited across trees. You can explicitly inherit an anchor-name from a...

This is similar to container-name for container queries, right? We don't make that one tree scoped? If you inherit container-name explicitly from a slot to a slotted element, we still...

> > If you inherit container-name explicitly from a slot to a slotted element, we still find that container with a query in the slotted element's tree. > > What...

So, my point about container queries is that the container queries spec is not making container-name a tree scoped name which means the text below is red (in both Safari...

> My example would be something like, uh: > > ``` > > > > > > > :host { > container-name: shadow; > container-type: inline-size; > width: 200px; >...

What makes this super complex in the case of anchor-name and container-name compared to at-rules like keyframes is that we have values both on the name and reference side which...

Hm, so given that css-scoping-1 says names/references must be tree-scoped names, perhaps the anchor positioning and container queries specs don't strictly need to say anything about it.

I'm utterly confused about the container queries case and need to go back to study it. There is the pseudo element thing affecting ::part() that I didn't think about in...

I agree that we should just close this. I have updated our impl to match the current spec and allow !important in style() query values.