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

@rniwa on top of the speed differences and possible search engine improvements noted above by contributors much more in depth with the topic:

1. Would custom elements be usable for scoping CSS (and CSR JS) to just one element and its children?
2.
  - Declarative ShadowDOM can be generated and/or validated with XML/XSD/XSL tools on the server side and then diffs
  - With the advent of WASM in the mid-far future there could be options to use SSR and DOM APIs but not JS to make apps more save/reliable and speedy and build thin clients such as via the [Phoenix Live View](
I have expected that too, but it can be engineerd very well to do SSR [Phoenix Live View approach](https://www.youtube.com/watch?v=8xJzHq8ru0M#t=30m5s ) if say MorphDOM was standardized tech accessible via the WASM layer.
  - For privacy mindet people having unobstrusive JS (e.g. basic working websites / services, if not with all fancy options) becomes an _option_ web developers CAN pick while still being able to scope CSS with Declarative ShadowDOM


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