- From: Matt Reynolds <notifications@github.com>
- Date: Tue, 15 Feb 2022 18:03:24 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 16 February 2022 02:03:36 UTC
> Maybe we could do something like addEventListener("gamepadchange", callback, { coalesce: false }) I like this. > The Generic Sensor API works around this by having start() and stop() methods With Generic Sensor you can create a new sensor object for each consumer but for Gamepad all consumers always see the same Gamepad object. We'd need to add a Gamepad.getGamepadSensor() method to return something that can be unique for each consumer so we can call its start() and stop() without interfering with other consumers. This could work but it seems overly complex to me. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/662#issuecomment-1041015506 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/662/1041015506@github.com>
Received on Wednesday, 16 February 2022 02:03:36 UTC