Issue metadata
Sign in to add a comment
|
Conflicting exit instructions when initiating WebVR presentation on an insecure context from VR browser |
||||||||||||||||||||||||||
Issue descriptionChrome Version: 61.0.3150.0 What steps will reproduce the problem? (0) Enable WebVR in chrome://flags. (1) From the VR browser, navigate to http://webvr.info/samples/insecure/test-insecure.html (2) Click the Enter VR button. What is the expected result? A. Permanent overlay: "Not secure" B. A temporary overlay containing detailed information about the implications along with instructions to exit. What happens instead? See the attached image Three overlays are displayed: A. Permanent overlay: "Not secure" B. Temporary overlay: "Press App button to exit" C. Temporary overlay: "Your connection to this site is not private. To exit VR mode at any time, remove headset and press back." Please use labels and text to provide additional information. Step 0 enables WebVR on insecure contexts, which are not supported by Origin Trials. (B) is displayed for all origins. I believe (C) was implemented before (B), and it existed before the VR browser was enabled by default. Now that the VR browser is enabled, the exit instructions in (C) should probably tell the user to press the App button (to return to the browser). With that, we can replace (B) with (C) on insecure origins.
,
Jul 10 2017
This is low priority at the moment because only users that flip the the chrome://flag for WebVR see (C). Also, it's possible that insecure origins will never be supported by default (see https://github.com/w3c/webvr/issues/249).
,
Jul 10 2017
Note: (B) is only displayed when starting presentation from within the VR browser. It does not appear if presentation is started from 2D Chrome.
,
Jul 10 2017
(B) fades after a few seconds, (C) sticks around for many more seconds, and (A) is permanent. (B) and (C) should be consistent OR when merging them, we should be conscious of whether we need to use a different duration when on an insecure origin. When following the steps, note that navigating to the URL in step (1) then entering the VR browser (by dropping the phone in the headset) will not work because the page auto-presents, meaning (B) is not displayed. However, you can hit the App button then hit the Enter VR button to see the three overlays.
,
Oct 12 2017
This is obsolete after issue 771223 . "Instead" strings (A) and (C) have been removed, leaving only (B) and its style. Any future UI work should ensure that the styles are consistent.
,
Jul 4
|
|||||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||||
Comment 1 by ddorwin@chromium.org
, Jul 10 2017