Re: [WICG/webcomponents] "open-stylable" Shadow Roots (#909)

@justinfagnani Thank you for your clarification.

Adding another clarification, nor does that sentence imply either that the original framing was only in terms of shadow crossing selectors combinators.

Rather, more importantly is the rest of the sentence "by necessary implication specificity, since that was the main/only approach at that time."

As the original issue clearly said, shadow crossing selectors combinators were never the main/only approach. They were presented just as a topic to consider.

But **specificity** was "the main/only approach at that time" (2020), since **priority** was not then available to author origins. That was implemented years later (2022) in @layer.

The [quoted comment](https://github.com/WICG/webcomponents/issues/909#issuecomment-1973774453) is about **priority** and begins, "I am hoping that _priority_ and _specificity_ are not related in a way that would block implementation to inheriting outer style layers into shadow trees".

I am not entirely sure why shadow crossing combinators have such a mindshare in this issue and keep coming up.

I hope it is clear I am suggesting something different: that **priority** (and repriortization) would be [a beneficial tool in shadow trees](https://github.com/WICG/webcomponents/issues/909#issuecomment-1971878378) over specificity alone, and @layer seems to me the logical starting point since that is exactly what it is for.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/909#issuecomment-1984766597
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/909/1984766597@github.com>