Allow GamepadDataFetcher to fetch data asynchronously. |
|||||
Issue descriptionIt would be nice if the GamepadDataFetcher could fetch controller data asynchronously, or if the GamepadDataFetcher itself was behind a mojo binding so that the controller implementation could live on another thread. For example, the VR controller isn't threadsafe, and needs to be used by the browser when rendering VR UI, so we have to push data from the VR rendering thread to the browser thread and cache it for when the GamepadDataFetcher requests it.
,
Apr 27 2017
,
Apr 30 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 2 2018
Brandon, can you comment on whether this would still be useful for WebVR? I think we are developing an alternate API for VR controller input so this may no longer be needed.
,
Aug 1
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by mattreynolds@chromium.org
, Apr 4 2017