- From: inoas <notifications@github.com>
- Date: Thu, 22 Oct 2020 01:20:19 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 22 October 2020 08:20:32 UTC
> @prlbr not a good idea but ok if you see any reason for that :) i wonder how you control the shadow dom content without javascript. That goes total into the wrong direction For instance through SSR such as Phoenix LiveView, as an example https://www.youtube.com/watch?v=MZvmYaFkNJI TLDR: It just pushes minimal diffs onto the DOM tree much like React but SSR-based using websockets. And declarative shadow DOM will become incerdibly useful for SSR (re)rendering parts of the application as separate components with separate concerns regarding styling. There are probably a few people who remember how CSS-rendering would get disabled when disabling Javascript back in Netscape Navigator 4.x. Restricting Shadow-DOM to JS only was/is the same limited mindset, finally getting corrected here <3. -- 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/831#issuecomment-714320436
Received on Thursday, 22 October 2020 08:20:32 UTC