Re: [WICG/webcomponents] [open-stylable] Collection of user stories (Issue #1052)

@michaelwarren1106, @rniwa:

It seems to be getting missed that modern browsers support "[Declarative Shadow DOM](https://developer.chrome.com/docs/css-ui/declarative-shadow-dom)".

The "user" in the above [use cases](https://github.com/WICG/webcomponents/issues/1052#issuecomment-2005229757) and [requirements](https://github.com/WICG/webcomponents/issues/1052#issuecomment-2005261539) is just the user of a shadow tree, particularly a declarative shadow tree.

To elaborate:

- Shadow trees are "just HTML" (a document fragment attached to a particular element, for which certain css rules apply).
- Shadow trees are not "Custom Elements" i.e elements upgraded by customElements.define() to have a Javascript class instance associated with them. This kind of "Custom Element" is often informally called a "web component" or a "Web Component".
- "Custom Elements" don't encapsulate anything.  Shadow trees do the encapsulating.

Declarative shadow DOM already gives web component users a way to present a shadow tree (with user-written CSS styles in it) to the web component.  And a way for the web component to accept, reject, or use those styles as it sees fit.

So user stories that boil down to something like "as a web component user I want the web component to consider using some styles I present to it in a shadow tree" is not a missing platform feature, it is a choice for web component authors to make.

What is missing is a way to bring page styles into shadow trees.

Without this common context, there seems to be a conflation loop.

Classifying as "push" vs "pull" vs "other" seem to suffer similarly.

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

Message ID: <WICG/webcomponents/issues/1052/2007862401@github.com>