Tracking :scope issue related to relative selector lists (:has())

[facelessuser]

So, when we implemented :has() we must have glossed over the requirement that :scope within :has() was supposed to refer to the element attached to the psuedo-class, and not the same element that :scope outside of :has() refers to.

With that said, it sounds like most implementers generally want to throw out this requirement much the same way that we did on accident 😅.

It sounds like, if things move forward the way that implementers are requesting, there may not be any need for us to change anything. This would be ideal for us. It is possible though, that some other requirement may fill the void that we do not currently support.

There is no actionable item yet as I do not plan on changing how :scope works in :has(), especially when browser implementors are currently contesting the requirement, but I'd like to track this issue in case things are settled in a way that it requires us to actually modify things.

w3c/csswg-drafts#6399

[facelessuser]

Turns out that special handling of :scope within :has() has been ruled as being removed. So there are no changes for us at this time.