Related: There is a related editor’s draft for Scoping Module level 1, though I’m not sure what the direction of that spec will be going forward, or it’s relationship to scoping in the Cascade.

FWIW, even if “scoped styles” aren’t going to be a thing (outside of the Shadow DOM), I like the way it’s explained in the Cascade spec now. Inline styles fit more neatly as a part of Scope, rather than an odd exception to the rules of Specificity.

FWIW, even if “scoped styles” aren’t going to be a thing (outside of the Shadow DOM), I like the way it’s explained in the Cascade spec now. Inline styles fit more neatly as a part of Scope, rather than an odd exception to the rules of Specificity.

Agreed.

Related: Selectors L4 also mentions the scoped <style> element in HTML.

Scoping has multiple effects, which can theoretically be triggered independently:

• scoping of selectors is in Selectors
• scope-precedence in the cascade is in Cascade

Since scoped styles have been mostly abandoned, the CSSWG resolved to drop scoping from Cascade L3. It's still in L4, however, in case anyone needs to refer to it. :)

WG resolution recorded at https://lists.w3.org/Archives/Public/www-style/2017Feb/0069.html