- From: Marcos Cáceres <notifications@github.com>
- Date: Tue, 20 Dec 2022 04:53:29 -0800
- To: w3c/gamepad <gamepad@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 20 December 2022 12:53:42 UTC
@7ombie I’m open to discuss this further, but… > This general agreement is highly unlikely to change. I’ve been chairing this working group for a while and this is honestly news to me? The Web Apps WG owns UI events, and a bunch of related specs. It might just be that the discussions didn’t happen in the context of this W3C working group? In any case, although it’s true that keyboard and mouse events can be bound to DOM elements, they can conceivably work without them… so what will we do about keyboard and mouse events if one is creating an application that works with multiple inputs? Won’t those events also need to be routed to a worker? Or is somehow gamepad events enough? -- Reply to this email directly or view it on GitHub: https://github.com/w3c/gamepad/issues/37#issuecomment-1359310827 You are receiving this because you are subscribed to this thread. Message ID: <w3c/gamepad/issues/37/1359310827@github.com>
Received on Tuesday, 20 December 2022 12:53:42 UTC