Re: [w3c/webcomponents] Is or how can Shadow DOM be 'SEO friendly'? (#500)

To add to @Nevraeka's point, isn't it the core principle of the web component specs to provide encapsulation and modularity as a set of primitive APIs? It would significantly subtract from their value if you added the stipulation: "unless you want SEO or A11y". This is especially true since JS libraries and frameworks are looking to web components as a foundation for their functionality.

I second @BronislavKlucka's proposal; it is a very pragmatic and forward-thinking idea. However, making `shadowRoot` available but, readonly means that it's tree is still mutable. Is it possible to make the entire tree immutable?

For reference, #505 was created in relation to this.

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