VR: Time out and return to browser when WebVR presentation fails to produce frames. |
|||||||||||
Issue descriptionWhen VR browsing is on by default and headset insertion always enters VR, in addition to (or maybe instead of?) checking if vrdisplayactivate fires requestPresent (or the page is already presenting), we should wait for a webVR frame to arrive, and time out if one doesn't arrive, returning to VR browsing mode. More generally, even during presentation, if a page stops sending webVR frames for any reason we should timeout and exit the presentation.
,
May 11 2017
We may want to handle these cases differently:
a) Failing to present on transitions
b) Problems after transitioning ("More generally.." and the bugs in #1)
,
Jun 7 2017
,
Jun 26 2017
,
Jul 20 2017
,
Jul 20 2017
We should have some kind of UI telling the user what happened as well. Please work with Josh/Gordon on this.
,
Aug 11 2017
,
Sep 6 2017
mthiesse@, it appears you may have (at least partially) addressed this with issue 713730, probably excluding the UI requirement in comment #6. Based on the intent of this bug, should it be closed as a dup, or changed to "provide UI if WebVR does not submit frames" or something?
,
Sep 22 2017
Given that we still need a bit of design here, let's push to M64 to give us time to work out the details.
,
Sep 22 2017
Closing this in favor of Klaus' bugs: ★ Issue 716087 WebVR: detect unrecoverable VR presentation issues ★ Issue 716071 WebVR: user feedback for underperforming app or device
,
Jul 4
|
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by klausw@chromium.org
, May 11 2017