Re: [gamepad] The API is not thread-safe and can not be fixed. (#18)

That will break existing code though. If we can break compatability, I'd have a stack per pad, with the browser on the bottom. Apps would 'take' a pad, and get pushed to the stack, and 'drop' the pad when they are done, and get popped off the stack for that pad. Whoever is on top of a stack has the pad all to themselves. An extension could take from the browser and still let the Web take the pad from the extension, and just wait for the webapp to drop it again. It seems like a better basis for the API.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/gamepad/issues/18#issuecomment-156212723