1366099 - Implement chrome-only API to report VR experience quality

Status: NEW

(Core :: WebVR, enhancement)

Description

[:kip (Kearwood Gilbert)]

In Bug 1362213, we are adding chrome-only API calls to allow the browser to toggle between it's own VR presentation and the content.  This will allow the browser and add-ons to display UI without interrupting the normally mutually exclusive WebVR sessions.

One of the primary use cases for this is to provide better transitions during WebVR link traversal and to present options to the user when content is not submitting frames to the headset.

In order for these interfaces to respond when needed, the quality of the WebVR content presentation needs to be accessible to the system and add-on code.  This can be exposed with a chrome-only API.

Bug 1362213 sets up some structures in the PVRManager protocol, which include details on the last 100 rendered VR frames.  In addition, it adds the concept of VR session "groups" and a "groupMask" for controlling visibility.  This will enable the performance of the WebVR content in a page to be reported independently of the add-on and system displayed interfaces.

As a start, we can expose the "input to frame submission" latency as a time duration recorded for each frame.  This should be sufficient for detecting when a site's performance has stabilized during link traversal or has dipped too low, while being independent of the variable framerate of HMD devices such as Oculus CV1 with ASW dynamically enabled.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The bug assignee didn't login in Bugzilla in the last 7 months, so the assignee is being reset.