-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Latest chrome updates broke vrview on mobile #306
Comments
Which version of Chrome exactly? There was a bug in Chrome 65 (https://crbug.com/805146) that should be fixed soon. See also the discussion in immersive-web/webvr-polyfill#307 (comment), including changes in Chrome 66. Updating the polyfill should handle the latter fine, but an upcoming Chrome update is required to fix the Chrome 65 issue. /cc @jsantell |
On chrome stable version 65.0.3325.109 |
Yes this is the same issue which came up with Android Chrome version 62.0.3202.84 last year and was fixed in subsequent versions. |
A new version of the polyfill containing a workaround for the Chrome 65 issue has been released: https://github.com/immersive-web/webvr-polyfill/releases/tag/v0.10.3 |
Looks like vrview is using 0.9.x, and uses WebVRConfig in unexpected ways; need to confirm if the YAW_ONLY option actually works (it's set after polyfill is brought in so looks like it wouldn't do anything), and how necessary mouse and keyboard controls (although it looks like it's using a different click/drag mechanism?) |
@ddorwin polyfill doesn't helps. Have yot tried it? |
@dkudrin do you have a test page using the latest polyfill release? what doesn't work? |
Visiting any webpage with a google vr frame with chrome on android, moving the smartphone the scene does not change visual as usual. Things remain the same in the cardboard view.
With firefox and samsung browser there are no problem
The text was updated successfully, but these errors were encountered: