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

> I don't know where that syntax even comes from, but it seems extremely out of place. Something like `@layer inherit(outside-layer-name as inside-layer-name)` would feel a lot more CSS than the weird dots that make it look like classes or some sort of indexing operation.

The simpler forms (`inherit`, `inherit.resets`) are still there.

But even a [prototypical](https://github.com/WICG/webcomponents/issues/909#issuecomment-1936910846) `<md-block>` web component with page styles could use multiple forms, see [user stories](https://github.com/WICG/webcomponents/issues/1052#issuecomment-2026303818):

27 Markdown component with automatic page styles
28 Markdown component with author-defined page layer
29 Markdown component with author-defined lower priority shadow layer
30 Markdown component with author-defined higher priority shadow layer
31 Markdown component with user-selectable page styles
32 Markdown component with page @scope

These directly address the subject of this issue and work with a declarative shadow DOM, a shadow tree created with this.attachShadow(), cascade @layer, and @scope without breaking or requiring change to any of them. And it's polyfillable.

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

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