- From: Mason Freed <notifications@github.com>
- Date: Sat, 15 Feb 2020 12:30:04 -0800
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Saturday, 15 February 2020 20:30:19 UTC
> 3. quickly verify that the SSR HTML matches the client-side vDOM (e.g. by computing a hash code of the SSR vDOM and storing it in the HTML, then checking that hash code against the hash code of the CSR vDOM) @dfabulich, thanks for the post. That made me understand the disconnect here. The point is that this proposal is **not** for a **full SSR system**. This proposal is for a necessary, low-level **primitive** that would be required for any Shadow-DOM-based SSR system. I'm not trying to solve your item 3 - that can be done a number of ways, and I'm not trying to propose a platform-standard way of diffing content. I suggested two *trivial* but *non-optimal* ways to do this: 1) always assume the SSR content matches and don't re-create anything, or 2) always assume it doesn't match and re-create it all. Clearly there are smarter, but more complex, solutions that can be provided by SSR frameworks. But no matter what the solution, there needs to be a declarative (no-JS) way to create a `#shadowroot` in the SSR content. That's what this proposal is all about. -- 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-586638558
Received on Saturday, 15 February 2020 20:30:19 UTC