- From: FND <notifications@github.com>
- Date: Thu, 03 Oct 2024 06:04:38 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 3 October 2024 13:04:42 UTC
@keithamus I don't disagree, but the original proposal quite intentionally limited its scope to the event context - in part because that seemed like a potential quick win[^1], but also for ergonomic reasons: Even if debouncing and throttling were available in some other form (via observables[^2], as stand-alone functions etc.), exposing such functionality via corresponding `addEventListener` options would still add considerable value IMHO. [^1]: Unfortunately, the enthusiasm here and elsewhere has yet to translate into interest by implementers though. Despite various efforts, it remains unclear how to get feedback from browser vendors. [^2]: FWIW, both debouncing and throttling had already been mentioned in WICG/observable#35. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/1298#issuecomment-2391371563 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/issues/1298/2391371563@github.com>
Received on Thursday, 3 October 2024 13:04:42 UTC