Early design review of light-DOM CSS Scope proposal (original) (raw)

HIQaH! QaH! TAG!

I'm requesting early TAG review of my proposal for light-DOM CSS Scope.

Previous scope proposals have attempted to address highly-isolated use-cases along side the more light-touch issues of namespacing and selector-proximity. Those attempts were largely abandoned in favor of Shadow-DOM solutions -- which strongly prioritize strong isolation. In the meantime, third-party tools (eg CSS Modules) and conventions (eg BEM) are more often used by authors to provide low-isolation scoping for light-DOM components. I'm proposing a native CSS approach to those use-cases.

• Explainer: https://github.com/oddbird/css-sandbox/blob/main/src/scope/explainer.md
• Security and Privacy self-review: This proposal does not expose anything new, and has no impact on security or privacy
• Primary contacts (and their relationship to the specification):
  • Miriam Suzanne, @mirisuzanne, Invited Expert, author
  • Mason Freed, @mfreed7, Google, contributor
  • Yu Han, @yuzhe-han, Google, contributor
  • Rune Lillesveen, @lilles, Google, contributor
  • Rossen Atanassof, @atanassov, Microsoft, co-chair
  • Alan Stearns @astearns, Adobe, co-chair
• Organization/project driving the design: CSSWG
• External status/issue trackers for this feature (publicly visible, e.g. Chrome Status):
  • Earlier discussion of scope on CSSWG: [css-scoping] Please bring back scoped styles w3c/csswg-drafts#3547

Further details:

• I have reviewed the TAG's API Design Principles
• The group where the incubation/design work on this is being done (or is intended to be done in the future): CSSWG
• The group where standardization of this work is intended to be done ("unknown" if not known): CSSWG
• Existing major pieces of multi-stakeholder review or discussion of this design: CSSWG Issue
• Major unresolved issues with or opposition to this design: No known opposition
• This work is being funded by: Google

We'd prefer the TAG provide feedback as 💬 leave review feedback as a comment in this issue and @-notify @mirisuzanne and @lilles