You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We would welcome your review of the Gamepad API specification, as part of our wide review before transitioning to Candidate recommendation (CR).
If there are any issues arising from your review, please file them on the Gamepad Github repo, and apply the "wide review" label to each issue. This will help us track your comments and respond accordingly.
If there are no issues arising from your review, please let us know by reply to this thread.
We would appreciate your comments no later than Friday 27th June 2018. Thank you.
The text was updated successfully, but these errors were encountered:
In case it helps, the plan proposed by @sgraham and @cynthia gostonwas to ship an initial version of the spec as it stands/is implemented, with a view to making more substantial changes in V2 - possibly with/within the WebXR space.
We've taken this up in the Seattle F2F, reviewed for any serious issues and was unable to find anything substantial that would warrant - say, unshipping the standard.
Some parts would be desirable to improve (e.g. getGamepads() being Promise based and behind a permission), an alternative to a polling model, and many other aspects that have already been reported in the past. We hope those aspects could be improved in the next iteration of the spec - presumably by having us take a look as early as possible.
We would welcome your review of the Gamepad API specification, as part of our wide review before transitioning to Candidate recommendation (CR).
If there are any issues arising from your review, please file them on the Gamepad Github repo, and apply the "wide review" label to each issue. This will help us track your comments and respond accordingly.
If there are no issues arising from your review, please let us know by reply to this thread.
We would appreciate your comments no later than Friday 27th June 2018. Thank you.
The text was updated successfully, but these errors were encountered: