A-Frame no longer responds to device motion on Firefox on Android after Firefox version 53.
Kip removed Cardboard support in bug 1250244, which caused the problem. However, A-Frame orientation still works on other non-WebVR non-Cardboard mobile browsers.
Why doesn't the WebVR polyfill kick in and wire up orientation API support?
- Use Firefox on Android, with any version after Gecko 53
- Open https://aframe.io/examples
- Move phone around
Expected: The scene is positioned relative to the real world.
Actual: The scene is positioned statically in the viewport, does not respond to device movement.
-
https://bugzilla.mozilla.org/show_bug.cgi?id=1250244#c40 Removal of Cardboard API support from Gecko, initial cause of problem.
-
https://bugzilla.mozilla.org/show_bug.cgi?id=1318293 Bug with discussion about orientation API specifically, and wherein QA provides regression range pointing to Kip's patch.
-
https://bugzilla.mozilla.org/show_bug.cgi?id=1318992 Bug filed specifically against Cardboard API not working, resolved WONTFIX.
-
https://bugzilla.mozilla.org/show_bug.cgi?id=1358506 Broken MDN demo on device orientation. turned out to be iframe xdomain issue - can't use orientation events in iframe from different domain.
-
immersive-web/webvr-polyfill#177 We thought maybe this was the cause. However, IIRC Diego updated the polyfill shipping in A-Frame long since, and the problem still exists.