-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setting frameData.pose (/w Origin Trial) #27
Comments
Yes, that's basically the issue, VRFrameData gets "nativised" after the page has loaded. I've tried a few workarounds, and I don't really like none because they're mean guaranteed breakage at some point, and I don't want to be troubleshooting full time. The current solution i have in dev, for instance, doesn't work with your page. So yay. To be honest, it's kind of annoying having to re-architect everything just because the combined hack of extensions injection and origin-trial enhancement. For now I rather developers be able to use the emulator -since they can work without enabling the origin-trial- and inconvenience the users that access origin-trial sites since, well, they didn't have a VR device to begin with. EDIT: it doesn't help either knowing that this is going to change, and rewriting the extension now doesn't exclude having to rewrite yet again in a few weeks. |
I think the only real option is to wait for the page to query for devices, and then start the API replacement… |
I've got this
|
I'm absolutely sure that this is covered by #21, though I thought it might be useful to log a specific example of Origin Trial issues.
When viewing a page with an active webvr origin-trial, I get the following error:
It looks like I'm passing a native
VRFrameData
object which has a readonly pose attributeThe text was updated successfully, but these errors were encountered: