Closed
Bug 1627331
Opened 6 years ago
Closed 5 years ago
Do not dispatch WebVR events when the display is used via WebXR API
Categories
(Core :: WebVR, enhancement)
Core
WebVR
Tracking
()
RESOLVED
FIXED
mozilla77
| Tracking | Status | |
|---|---|---|
| firefox77 | --- | fixed |
People
(Reporter: mortimergoro, Assigned: mortimergoro)
References
Details
Attachments
(2 files)
Right now WebVR events are fired when using the WebXR API. This causes Aframe demos to exit VR after 2-3 frames. Aframe is receiving a vrdisplaypresentchange event, and they exit VR if the VRdisplay is not presenting.
| Assignee | ||
Updated•6 years ago
|
Assignee: nobody → imanol
| Assignee | ||
Updated•6 years ago
|
Summary: Not not dispatch WebVR events when the display is used via WebXR API → Do not dispatch WebVR events when the display is used via WebXR API
| Assignee | ||
Comment 1•6 years ago
|
||
| Assignee | ||
Updated•6 years ago
|
Type: defect → enhancement
Pushed by igorostizaga@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/5c7fdf2a3d71
Do not dispatch WebVR events when the display is used via WebXR API r=kip,daoshengmu
Comment 3•5 years ago
|
||
Comment 4•5 years ago
|
||
After applying this patch, Hubs can be run in FxR Quest, but its view orientation is inverted. So far, except for Hubs, all other examples are good.
Comment 5•5 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox77:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla77
You need to log in
before you can comment on or make changes to this bug.
Description
•