Support Daydream's 2D-in-VR rendering path.
Basically, this CL ensures that when Daydream's 2D-in-VR path is enabled that we (almost) never show VR-supporting chrome activities in 2D when the user is in headset, even if Chrome is launched with a 2D intent. Intents sent to the 2D launcher that can be supported by VR rendering are forwarded to the VR launcher when the user is in headset (intents that aren't supported by VR rendering will still show in Daydream's 2D-in-VR rendering path). If a ChromeActivity that supports VR is launched directly while in headset, we just add the Daydream category to the intent and continue with intent processing as usual. If, somehow, Chrome was launched in 2D, then resumed while in headset, Chrome will still render using the 2D-in-VR flow. This is fine for now as Chrome will still be usable, and this situation is very difficult to get into, but the user will probably be confused :P This CL also avoids showing the request to exit VR prompt when 2D-in-VR is supported, favoring immediately switching to 2D rendering mode and showing the dialog or launching the Activity that triggered the request, then returning to VR rendering after returning to Chrome. Bug: 826732 Change-Id: I1a09f201554e4e3171f5657b0fb667acc6f4c784 Reviewed-on: https://chromium-review.googlesource.com/999997Reviewed-by:Ted Choc <tedchoc@chromium.org> Reviewed-by:
Yash Malik <ymalik@chromium.org> Commit-Queue: Michael Thiessen <mthiesse@chromium.org> Cr-Commit-Position: refs/heads/master@{#549248}
Showing
Please register or sign in to comment