Assigning to Chris for now since he's working on menu mode.

Feel free to reassign.

 Issue 690165  has been merged into this issue.

I'll start on this one today.  In a nutshell, I think a sample flow looks like:

- Start on a conventional page.
- Link/navigate to a WebVR page.  We'll see the page on the quad, where it may suffer from "magic window on a quad" syndrome.  This is a separate issue.
- Click the "Enter VR" button on the page.  Page should start presenting, and UI should transition to WebVR mode (no buttons or other elements, other than the transient URL indicator and security warnings).
- Clicking the app button should bring up menu mode.  WebVR content should stop receiving head poses and input.  What we actually render for the content is TDB - a frozen image on a quad, nothing, etc.  Initially, we'll just completely hide WebVR content and draw the grey background instead.
- Exiting menu mode should return to WebVR presentation.
- Clicking the menu mode "back" button should exit presentation, returning the user to the page on a quad.
- A second "back" navigation should then return them to the non-WebVR page the user originated at.

A few test cases:

- While in presentation, clicking a link to a different site must return the user to shell mode (whether a webVR site or not).
- The same should be true for navigation triggered from the menu.

Brandon is interested in constructing a WebVR test page that explicitly links to conventional content.  That'll be handy for testing cases above.

Brandon and Adam, if you see issues with the flow above, let me know...

How do WebVR pages link to conventional content?  Are they just setting window.location?

The scenario's you describe in #5 sound good.

FYI: There's a test page for linking at https://webvr.info/samples/test-vr-links.html (Also found from https://webvr.info/samples/ at the bottom, labeled "VR Links")

On this page looking at one of the boxes and clicking will trigger a window.location navigation. One links to a 2D page, one links to a WebVR-enabled page. (Sorry, I've forgotten which is which.)

In light of the v0 spec, the UX for entering and exiting a WebVR presention in VrShell has changed. See issue 713377 for more details.