Change hit-test resolution to return results as part of FrameData to ensure correct timing of results |
||||||||||||||
Issue descriptionCurrent implementation relies on the way frames are generated on the renderer side and the ordering of callbacks through mojo. More robust design would be to return hit-results as part of frame data and then re-map results to the original promises on the renderer side. this would be more robust to future/different frame generation approaches on the renderer side.
,
Jun 8 2018
,
Jul 4
,
Jul 11
,
Aug 7
Removing Blink>WebVR component and assigning to Blink>WebXR
,
Aug 7
Removing Blink>WebVR component and assigning to Blink>WebXR
,
Aug 7
,
Aug 10
We should look at this once the web API questions have settled since that could affect the implementation.
,
Aug 10
,
Aug 29
This will heavily be influenced by potential changes to the WebXR API and relative-object support for hit-test API - we may require passing a XRFrame object back as part of the hit-test resolution in which case we will have to cache the hit-test callbacks until we get the frame data and can construct an XRFrame object.
,
Aug 29
Rethinking how complex this will be
,
Sep 4
,
Sep 20
downgrading to P3. If spec changes though (@lincolnfrog - please link related issue) this may be required (P1).
,
Sep 21
Blocked on resolving spec issues such as https://github.com/immersive-web/webxr/issues/403
,
Sep 26
|
||||||||||||||
►
Sign in to add a comment |
||||||||||||||
Comment 1 by mthiesse@chromium.org
, May 29 2018