- From: Jake Archibald <notifications@github.com>
- Date: Thu, 04 Jan 2018 02:33:05 -0800
- To: w3c/gamepad <gamepad@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 4 January 2018 10:33:29 UTC
@pyalot > I'm not sure why you'd call it Coalesced events. I'm not calling it that. It already exists for pointer events https://developer.mozilla.org/en-US/docs/Web/API/PointerEvent/getCoalescedEvents. > You get a list of events that occured since last time you called that function. Not really, you get a list of events that were coalesced into that render step event. If you don't call `getCoalescedEvents`, those additional events are gone. If it behaved as you describe, it'd be a massive memory leak – you'd quickly have millions of events buffered in memory that couldn't be collected. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/gamepad/issues/4#issuecomment-355249506
Received on Thursday, 4 January 2018 10:33:29 UTC