- From: Joe Pea <notifications@github.com>
- Date: Mon, 06 Sep 2021 22:06:27 -0700
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 7 September 2021 05:06:40 UTC
> While I don't think an event-based approach to this problem will be entertained due to performance reasons, it doesn't seem difficult to polyfill this behavior. I don't understand why we think performance is an issue with events. If there are events attached, DOM change events can be handled synchronously, and that machinery can be enabled _only if_ an event listener is added. Secondly deferring or batching event handling off of the synchronous events is literally no more difficult than using something like `MutationObserver`. `MutationObserver` has a worse developer experience than someone simply deferring their updates manually. Furthermore, it would be simple to add an event option like `{deferred: true}`, and the developer experience would be yet even better. I think we can make the web both easier to work with, and have performant options. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/933#issuecomment-913993039
Received on Tuesday, 7 September 2021 05:06:40 UTC