Re: [WICG/webcomponents] Should browsers do bookkeeping on DOM parts after initial parse? (Issue #1030)

We’re going to look into seeing if we’re doing anything egregious. I guess
if we’re using ChildNodePart.replaceChildren with a document fragment, the
operation to update parts should be pretty cheap.

I was thinking with a normal dom element, you’d have to track its owner
part and move the related parts accordingly, but we’re not exactly doing
that.

On Fri, Sep 15, 2023 at 12:49 PM Ryosuke Niwa ***@***.***>
wrote:

> Why is supporting getParts() to be updated so expensive? It seems like an
> implementation problem to me.
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/WICG/webcomponents/issues/1030#issuecomment-1721068942>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AA2MCG4HSHW2E25UIAWDYWDX2QXEHANCNFSM6AAAAAA4ZR4NWQ>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>


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

Message ID: <WICG/webcomponents/issues/1030/1721280308@github.com>