- From: Reilly Grant <notifications@github.com>
- Date: Tue, 17 May 2022 10:53:12 -0700
- To: w3c/gamepad <gamepad@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 17 May 2022 17:53:24 UTC
Re-opening this issue because I agree that regardless of whether or not events are added to the Gamepad API sites should be able to receive and handle these events from a worker. Unlike mouse and keyboard input, gamepad input isn't tied to a particular DOM element and so doesn't have any of those issues in being brought to a worker. @marcoscaceres, can you elaborate on your earlier message about exposing events in a worker not making sense? -- Reply to this email directly or view it on GitHub: https://github.com/w3c/gamepad/issues/37#issuecomment-1129153772 You are receiving this because you are subscribed to this thread. Message ID: <w3c/gamepad/issues/37/1129153772@github.com>
Received on Tuesday, 17 May 2022 17:53:24 UTC