- From: Marcos Cáceres <notifications@github.com>
- Date: Tue, 13 Dec 2022 16:58:47 -0800
- To: w3c/gamepad <gamepad@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/gamepad/issues/37/1350194495@github.com>
> WebUSB, WebHID and WebSerial are all available in workers. WebMIDI will support workers soon, and WebBluetooth intend to support workers, but haven't finalized the details. Web MIDI aside, none of those are web standards unfortunately. It's hard to discuss the merits of those specs as they currently stand, as they are single implementer features that have, to date, received limited architectural input from multiple implementers. **That's not to say that the model/architecture on which those specs are built is in any way deficient**, but there has just been a lack of scrutiny so it's not possible to confidently say anything one way or the other. > as every other global input API does or plans to do already. As above. There is no agreement in the web community that the model for the APIs you mentioned is correct and one the working groups should universally follow - so it would be premature to make any architectural decisions based on the specs you listed. Having said that, it would be worth while having a generalized discussion with the TAG around this topic. In that context, WebUSB, WebHID and WebSerial, etc. would be great to discuss. It would also be great to also consider how the events model #152 could come into play here 🤔. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/gamepad/issues/37#issuecomment-1350194495 You are receiving this because you are subscribed to this thread. Message ID: <w3c/gamepad/issues/37/1350194495@github.com>
Received on Wednesday, 14 December 2022 00:59:00 UTC