Re: [WICG/webcomponents] Add getElementsByPartName() that returns live collection. (Issue #964)

@rniwa,
>We don't want to add a new live NodeList / HTMLCollection since they slow down DOM operations of the entire document due to various implementation constraints.

Live NodeList is a generic pattern people found quite useful and is a part of standard. I do not understand the reason of restraining developers of such useful pattern. It is an app developer decision whether the performance impact critical or not.  

The Part is just one of the nodes in the DOM. What is the reason to make it an exception from generic DOM API?
I do not see the given "not performant" as an excuse. If generic DOM API good enough, let it cover the whole DOM including Parts. 

With all due respect. this ticket has to be reopened at least to collect opinions from potential consumers. The question on subject did not appear from the sky. It is a valid pattern and many app developers would be willing to sacrifice some performance in order to make data-responsive page. Most of such uses would be applied on already generated static page where performance would be spent exclusively on serving the binding, ideally via live NodeList. Such use case has NO impact on DOM performance.    

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

Message ID: <WICG/webcomponents/issues/964/1229306648@github.com>