Closed Bug 1288193 Opened 4 years ago Closed 4 years ago

[webvr] Slow to enter VR

Categories

(Core :: DOM: Core & HTML, defect)

defect
Not set

Tracking

()

VERIFIED FIXED
mozilla51
Tracking Status
firefox51 --- fixed
firefox56 --- verified
firefox57 --- verified
firefox58 --- verified

People

(Reporter: caseyyee.ca, Assigned: kip)

References

Details

(Whiteboard: [webvr])

Attachments

(1 file)

When Entering VR, it seems to take 3-4 seconds before anything shows in the headset and when onVRPresentChange is fired.  

This causes users to either click "Enter VR" again, or think that VR is not functioning.  

Not sure if this is a Oculus issue or with something with FF?
Flags: needinfo?(kgilbert)
Assignee: nobody → kgilbert
Flags: needinfo?(kgilbert)
Ideally, content should respond to the user immediately on requestPresent to prevent users from clicking multiple times while the promise is resolved; however, this delay does seem rather long and will need some investigation.

Even if not the case for currently supported VR hardware, content must assume that requestPresent could take multiple seconds due to powering up hardware or waiting for security prompts to be accepted
Blocks: webvr
Component: General → DOM
Product: Firefox → Core
I have found the source of the bug.  Patch is incoming..
Attachment #8787778 - Flags: review?(gwright)
Comment on attachment 8787778 [details]
Bug 1288193 - Ensure that the content process receives the presentation status of a VRDisplay immediately after adding or removing layers

https://reviewboard.mozilla.org/r/76464/#review75234
Attachment #8787778 - Flags: review?(gwright) → review+
Pushed by kgilbert@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/89b9735661b9
Ensure that the content process receives the presentation status of a VRDisplay immediately after adding or removing layers r=gw280
https://hg.mozilla.org/mozilla-central/rev/89b9735661b9
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla51
I re-verified using Fx56.0-build6, Fx 57.0b5 and Fx 58.0a1 (build ID: 20171004100049) on Windows 10 x64 and I can confirm this issue is fixed.
Status: RESOLVED → VERIFIED
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.