Closed lcgao closed 2 years ago
dom.vr.enabled=false
disables the deprecated WebVR spec. We did that because we just want to focus on WebXR and not maintain deprecated APIs
Okay, understood.
So jus for now, is there any risk if I enable WebVR in Wolvic?
I don't think there is any risk, just that if your users encounter any issues with WebVR content we could not obviously prioritize them as it's officially unsupported by Wolvic
Okay, clear. Thank you.
Configuration
Wolvic version: main branch - noapi Wolvic build ID: main branch - noapi
Hardware:
Steps to Reproduce
Current Behavior
Website content rotates(right-left, up-down) in the opposite direction(left-right, down-up)
Expected Behavior
Website content rotates(right-left, up-down) in the direction as expected(right-left, up-down).
Possible Solution
I found the key point is in this commit: https://github.com/Igalia/wolvic/commit/80a501266bbbb9b7f47d99cde14bd69a630730fd#diff-7ed70199d3f1b35b205846662071f83d9e5b8927d5c493d862505da0d6b9d975R11.
So why set
dom.vr.enabled
to false? And is there any risk if I set it to true again?Context
Error Logs and Stack Traces