Re: [WICG/webcomponents] [dom-parts] Tree structure of parts in the DOM (Issue #992)

From prospective of the frameworks needs, the traversal is just a part of more general solution: the DOM with template render results merging. Perhaps it worth to propose the API for merging the alive DOM with detached one?   

Browser would perform this operation way more efficient then JS as has ability to use threads on simultaneous DOM sub-trees inspection. Of course if exposed to JS API would have async nature.

As the detached DOM just have to follow the Node interface, the data layer for it could be served by wrapper from the POJO HTML presentation, virtual DOM,  XML, etc.

Going further, as the data to detached DOM transformation can be a streaming/ multithreaded process, the API can be exposed as the template engine method which instead of rendering own result would merge the results into live DOM.

🤔 perhaps worth own proposal?

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

Message ID: <WICG/webcomponents/issues/992/1657551259@github.com>