In order to ensure the best experience, WebGL contexts for WebVR content should be created on the display adapter that the VR display is physically connected to. Rather than changing all WebGL contexts to use the adapter with connected VR hardware, we should force context loss when the VRDisplay.requestPresent call is made and re-create the context on the optimal display adapter. A preference should be added to force the browser to always force context loss on VRDisplay.requestPresent even when the existing context was created on the correct adapter. This will enable WebVR developers to test their sites and ensure that they respond to the events appropriately.
Moving to p3 because no activity for at least 24 weeks.
Priority: P1 → P3
You need to log in before you can comment on or make changes to this bug.