Re: [w3c/gamepad] Make gamepads accessible by web worker (#37)

@marcoscaceres - Ultimately, keyboard and pointer events will need to be exposed to workers (for example, you could image a DAW plugin that is controlled with a mouse, or a graphics app that lets you use a touchpad gestures to draw and paint), but that requires new APIs for global keyboard and pointer events (unrelated to the DOM), as the DOM is pretty much married to the main thread.

Note: The Input for Workers Proposal has been abandoned.

The Gamepad API is not related to the DOM, so doesn't need a separate proposal to support workers.

Ultimately, if we want the Web to be capable of desktop-style applications, it needs to be able to handle *every kind* of user input in workers. Low latency response to user input is just that fundamental.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/gamepad/issues/37#issuecomment-1360260690
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/gamepad/issues/37/1360260690@github.com>