Re: [whatwg/dom] Declarative Shadow DOM (#510)

> It's naive to think that all robots will eventually adapt. Some many don't execute JS or may parse the document in many different ways.

As it is declarative `<shadowroot>` it's no longer JS to execute, it's just a new HTML Element.
Demand for **all** users to adapt is, as [already stated here](https://github.com/whatwg/dom/issues/510#issuecomment-329324736), "general counter-argument against any addition to HTML"

My point is that Declarative Shadow DOM, would work not worse, but even better than, already shipped imperative Shadow DOM. And the fact that there _is_ a problem with Shadow DOM and SEO **in general** shouldn't block us from moving forward. Especially, given that **if** robots would adapt to the new element, it could actually solve this issue.

To me, SEO is a general problem of Shadow DOM, not just declarative one, and declarative SD finally gives a chance to all the robots that read just HTML to reason about it.

> Shadow DOM isn't a security feature, only encapsulation. DOM for interoperability, styling for limiting side-effects. Not having access to content is a problem.

I agree it's not a security feature. But this encapsulation creates an isolation boundary. Then the fact that somebody hits this boundary because he/she was not prepared to consciously do that, is the actual feature of the Shadow DOM to me.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/510#issuecomment-338961845