- From: Tom Wilkinson <notifications@github.com>
- Date: Tue, 21 Mar 2023 15:10:25 -0700
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 21 March 2023 22:10:37 UTC
Oh I think not doing this feature at all would be a shame! if it's essential to you that "updating multiple parts of the DOM" be in the v1 of this API, I think it's something that warrants discussion. In my discussions with frameworks at Google, that has not been the feedback I've gotten about the direction of a DOM parts API, and most people seem more excited about more performantly locating nodes than updating them. I think having a feature to more optimally locate nodes for updating is great new feature. I think that being able to make DOM updates more performant is also a great new feature. I just think if I had to plan this out, locating nodes is the logical first feature to land, and updating nodes would be an addition. -- Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/991#issuecomment-1478655414 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/991/1478655414@github.com>
Received on Tuesday, 21 March 2023 22:10:37 UTC