Bug 1757431 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Saw while adding support for the https://developer.mozilla.org/en-US/docs/Web/API/ScreenOrientation/lock api on Fenix 
by implementing the https://bugzilla.mozilla.org/show_bug.cgi?id=1697647 and https://bugzilla.mozilla.org/show_bug.cgi?id=1744101 GeckoView callbacks
in https://github.com/mozilla-mobile/fenix/pull/24027 and https://github.com/mozilla-mobile/fenix/pull/24027
that after we get the unlock callback from GeckoView, switch to another tab then return to that same tab which previously called `onOrientationUnlock` we immediately get an unexpected `onOrientationLock` call and as such the app will try to set an orientation lock.

This seems like a bug in GeckoView which doesn't update an internal state to know that orientation lock finished.
Saw while adding support for the https://developer.mozilla.org/en-US/docs/Web/API/ScreenOrientation/lock api on Fenix 
by implementing the https://bugzilla.mozilla.org/show_bug.cgi?id=1697647 and https://bugzilla.mozilla.org/show_bug.cgi?id=1744101 GeckoView callbacks
in https://github.com/mozilla-mobile/fenix/pull/24027 and https://github.com/mozilla-mobile/android-components/pull/11789
that after we get the unlock callback from GeckoView, switch to another tab then return to that same tab which previously called `onOrientationUnlock` we immediately get an unexpected `onOrientationLock` call and as such the app will try to set an orientation lock.

This seems like a bug in GeckoView which doesn't update an internal state to know that orientation lock finished.

Back to Bug 1757431 Comment 0