☂ Address scenarios that currently cause the VR browser to bail out of VR |
|||||||||
Issue descriptionCurrently, there are some rare scenarios that are not correctly handled in the VR browser and cause the user to be returned to the 2D browser outside the headset. Examples include issue 726744 , issue 727373 , issue 722861 , and issue 722859. We should ensure that we correctly handle these so that users are never forced or asked to exit VR to accomplish a (required) task or view web content.
,
Jun 20 2017
Should this be on the M-61 hotlist? The bail-outs are generally meant to allow M-61 to ship. I think I should be filing individual bugs for bail-out cases, targeting them for M-62, and addressing them one by one as time allows. David, how does that sound?
,
Jun 22 2017
It is a "want" for M61 - I've lowered the priority. Yes, we should file individual bugs for the [groups of] cases. This is an umbrella bug for all of those. One thing we need to do is make sure we have a list of all those cases. In the end, we will probably end up with some in M61 and others not. Once we have documented them, we can probably remove or change the M- label.
,
Jul 7 2017
,
Aug 9 2017
This was not associated with this umbrella bug, but cjgrant@ fixed one of the reasons here: https://codereview.chromium.org/2945173006/
,
Aug 9 2017
,
Aug 9 2017
,
Aug 9 2017
I've created sub bugs for each of the issues. Milestones are attached to those, so I can remove the milestone here.
,
Apr 17 2018
We've addressed the blocking bugs against this one. Closing it off.
,
May 10 2018
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by ddorwin@chromium.org
, Jun 9 2017