Re: [w3c/webcomponents] Allowing serialized access to custom element implementation DOM for web archival benefits (#657)

Thanks for the example 👍

This works, if:
1) I own the page and know what goes into it all the way to the child leaf node.
2) The APIs that the custom element depends on (and draws data from) is still alive (problematic for a web archive).

As we know, the initial state of a web app could be an empty `index.html` shell (Initial State), which is then followed by JS loading, AJAX calls, and injection of more DOM elements into the shell (-> Rendered State). Before custom elements, as it currently stands, it is trivial to capture the entire DOM in the Rendered State: `document.documentElement.outerHTML` gives me everything in the Rendered State. 

So my goal is really to capture the Rendered State of the HTML DOM as it is. And the 2 points above does not apply: I don't own the page, and the APIs that the elements depend on may not exist anymore. Pre custom elements, this is not an issue as illustrated above, I can still render the Rendered State irregardless of API availability. With custom elements, it seems like there isn't a way to get the entire Rendered State of the page. Hope I make sense.

Is there a way to capture the Rendered State of a Custom Elements page all the way down to the child leaf node?



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/657#issuecomment-324455944