New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 763000 link

Starred by 1 user

Issue metadata

Status: ExternalDependency
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Compat
Proj-XR



Sign in to add a comment

WebVR partner site https://bear71vr.nfb.ca/ takes a long time to load and doesn't display intro msg

Project Member Reported by dbbrooks@chromium.org, Sep 7 2017

Issue description

Chrome Version: 62.0.3202.8
OS: Android M, N
VRCore: 1.8.163477258
Device: Galaxy S6, Pixel
Headset: Happens on both Cardboard and Daydream

Note: This does not happen with 61.0.3163.79

There are multiple issues that are occurring with this site. And noe of them occur in M61.


What steps will reproduce the problem?
(1) go to https://bear71vr.nfb.ca/ and press enter VR button 
(2) Place device in headset (sync controller if using Daydream)


What is the expected result? The normal behavior for this site is to start a WebVR presentation, the content is a dark environment, and a logo appears, then disappears, then an intro msg appears and disappears, then a video, and so on.

What happens instead?

- Intermittently a few seconds after starting the WebVR presentation, the device switches back to 2D mode.
- There is a long black screen after starting the WebVR presentation. Much longer than normal. 
- The logo and an introduction msg screens are skipped, are really dark, or disply really slowly.
 
Do you have the chrome://flags set? Sites don't have the M62 Origin Trial tokens yet. If so, they may not have updated to handle the changes in the M62 Origin Trial.
Yep, both webvr and gamepad extensions flags are enabled.
Yeah, this is just them not having updated for the changes in the M62 OT. They probably need to fix their autoplay to use the gesture token in vrdisplayactivate, and show a splash screen if they're taking more than 5 seconds to load.
Components: -Internals>VR Blink>WebVR
Labels: M-62
Owner: meganlindsay@chromium.org
Status: ExternalDependency (was: Untriaged)
See also  issue 762627  for the same site.
Oh, I'm probably mistaken with the autoplay comment. I don't think they support detecting headset insertion in the first place.
Is this just the 5 s loading timeout then?
Owner: paezagon@chromium.org
Status: Available (was: ExternalDependency)
The intermittently switching back to 2D mode is a duplicate of 762627, but the other issues (long black screen, logo and intro issues) are new. Unclear why this is happening in M62 and not M61.
Owner: meganlindsay@chromium.org
Status: ExternalDependency (was: Available)
Confirming that the switching back to 2d is the five second timeout change. Reverted that change locally to bypass the issue in order to look into the other issues. 

The logo and intro messages are displaying, they simply cannot be seen because there is a fade in from black that is taking a very long time. This and other animations (including the animated video close button) all seem to be running at a very slow framerate, unlike the map animations. This seems to be related to the M62 OT window.requestAnimationFrame() changes, as reverting that change causes the issue to go away, so the developers probably need to fix anything that is using that function (I saw at least three instances of it).

Also, it seems that none of the click actions are working, which probably means they need to update to the gamepad API. 
Labels: Type-Compat
Update - this still repros on Chrome 64.0.3274.0
Owner: sko...@chromium.org
Labels: -M-62 M-67
This still repros on Chrome 66.0.3355.0 in both Cardboard and Daydream. Verified it with Pixel 2 with Android 8.1.0  The initial black takes so long that you feel like the device shutdown.  Being extremely patient results in the fading in of everything and eventually the video appears.  Once the video is there thinks seem to move better.
Labels: Test-Complete
Labels: -M-67 M-68
Components: Blink>WebXR
Labels: BlinkWebXR
Removing Blink>WebVR component and assigning to Blink>WebXR 
Labels: -BlinkWebXR
Removing Blink>WebVR component and assigning to Blink>WebXR 
Components: -Blink>WebVR

Sign in to add a comment