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

> Thanks for feedback. We are totally aware that Declarative Shadow DOM would address some use cases, such as an alternative of scoped css.
> However, our consensus at Tokyo f2f is that we are not enthusiasm to update the parser only for supporting Declarative Shadow DOM. As @tomalec mentioned in [#510 (comment)](https://github.com/whatwg/dom/issues/510#issuecomment-370980398), supporting non-scripting environment is not sufficient motivation for updating the parser, for a while.

Unless there is another way to scope, limiting this dom feature to JS only is a step back into dark times where during Netscape 4 times if you disabled JS, CSS would stop working.

Given the adoption phase of web tech to be quite long, implementing declarative shadow *at this time* would boost the whole web tech stack a few years down the pipe. Why? Because together with the new 0 specifity selectors there is finally an easy way to style components and people will stop overwriting and extending huge CSS files.

The vast majority on the web are amateurs and you are denying them tools to work easy and in a clean fashion.

-- 
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-591920836