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

> Why is supporting getParts() to be updated so expensive? It seems like an implementation problem to me.

I tend to agree - I’d refrain from making API decisions too early based on the early prototype. I haven’t had much time to optimize and it’s likely there’s something easy that could be fixed in replaceChildren.

That said, it’d be good to have the debate about whether tracking is *necessary*, because it certainly has non-zero overhead. Removing it will make the basic operations faster. But I don’t know if removing it will make the *usage of the API* faster, since it might require more work to be done on the framework side.

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

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