1188199 - There should be a standard way for users to Enter Web VR content and Zero orientation/position sensor.

Status: NEW

(Core :: WebVR, enhancement)

Description

[Casey Yee]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2464.0 Safari/537.36

Steps to reproduce:

How a user opens Web VR content into a headset is entirely up to how the content developer implements the VR API's: Entering VR via requestFullscreen({ vrDisplay: vrDisplay }).   The same goes with zero'ing the orientation/position sensors.





Actual results:

This leads to confusion for users since everyone will implement this behavior differently:
ie:

Entering VR:
www.mozvr.com -> Goggle icons which the user clicks.
player.elevr.com -> Press 'F' to enter VR.
mozvr.github.io/panorama-viewer -> double click to enter VR.

Resetting sensor:
Some use 'Z' = zero sensor, or 'R' = reset sensor, sometimes not even implemented at all.


Expected results:

Provide some kind of consistent UI for users to Enter VR or Reset headset sensors.

Comment 1

[Casey Yee]

I should also point out that ESC to "exit" VR is behavior inherited from requestFullscreen -- but this should also be considered.

Comment 2

[Chris Peterson [:cpeterson]]

Casey, thanks for testing WebVR!

Josh: how should WebVR UX feature requests be triaged?

Comment 3

[Josh Carpenter [:jcarpenter]]

Hi Chris, best to slap a [webvr] whiteboard tag on it and needinfo myself and Marco Mucci, thanks. :)

This item came out of a UX discussion the front end / UX team had yesterday. There are several ways we can approach this, and next steps are on our team to generate potential solutions and prioritize, then bring to desktop team as is appropriate.

Comment 4

[:kip (Kearwood Gilbert)]

We now have VRDisplayActivate events to tell a web page to enter VR, and just need it hooked up to a button or keypress in the UI.  This event should be triggered with the "requested" reason code if activated from UI.

Sensor reset is now handled by the VR platforms themselves through a UI provided by either Oculus or SteamVR.  This is not needed in the browser itself.

Comment 5

[:kip (Kearwood Gilbert)]

Bug 1362213 will be landing a chrome-only API that would enable the "enter vr" button in the browser chrome.