[Bug]: Immersive mode in release, multiple devices (regression in 97)

[yoasif]

Steps to reproduce

Sounds like #23119

I've noticed that this bug occurs , when you Fullscreen a page/ video (YouTube, etc.)

Expected behaviour

No immersive mode.

Actual behaviour

I'm annoyed having to swipe up first to unhide the navigation bar if I want to hit the Back button.

Device name

Affects at least:

• Xiaomi 11T Pro
• Oneplus 8T (Android 11)
• Xiaomi poco f3 (lineageos 18.1)
• Samsung galaxy A12 (Android 11)
• Moto E4 (Android 7.1.1)
• Samsung Galaxy s10+ (Android 12)
• Pixel 2 (Android 11)
• Samsung Galaxy S5 (Android 6)
• honor 8x (Android 10)

Android version

Android 10, 11

Firefox release type

Firefox

Firefox version

97.1.0

Device logs

No response

Additional information

Also reported on https://www.reddit.com/r/firefox/comments/sp5nox/disable_immersive_mode/ and https://www.reddit.com/r/firefox/comments/sqqsjf/firefox_on_android_hiding_top_and_bottom_bars/

Users say that this does not reproduce in 98.0.0-beta.1 or nightly.

┆Issue is synchronized with this Jira Task

[sir-pinecone]

I'm also experiencing this on One Plus 5T (Android 9).

[bradleyharden]

This affects my Sony Xperia XZ1 Compact (G8441) on Android 8 as well.

[dootingalong]

Reporting this also happening on OnePlus 7 Pro with Android 11

[kbrosnan]

Pretty sure this is mozilla-mobile/android-components#11527 which needs a 97.2.0 build cut.

[bmaverick24]

This is happening to me as well on Google Pixel 3 running Android 11

[erikhubers]

Can confirm this is also happening on Android 11 on my Xiaomi Poco F3 (M2012K11AG) running lineage_alioth-userdebug 11 RQ3A.211001.001 10039287.

[bio12]

Can confirm. Android 12, Samsung S10+
Unusable with this behavior.

[majik-sheff]

Behavior confirmed.

FF build info
97.1.0 (Build #2015860771), 365e9fb+
AC: 97.0.10, d6ce171289
GV: 97.0-20220131171509
AS: 87.1.0

Add-ons:
Ublock Origin
Noscript Security Suite
Video Background Play Fix

Pixel 5
Running Android 11
4.19.135-g3fdbc8e39c0d-ab7132628
#1 Mon Feb 8 18:40:22 UTC 2021

[majik-sheff]

Behavior seems to stop when "Video Background Play Fix" addon is disabled. Will report any further discoveries.

Update: After locking and unlocking the phone the behavior returns. It appears that simply going into the extensions manager is enough to trigger a temporary "fix".

[mintyglue]

Same issue: Realme 6S, Android 11

[bio12]

Disabling "Video Background Play Fix" works. Thanks.
Update: after a while problem continues with disabled addon.

[mintyglue]

Disabling "Video Background Play Fix" works. Thanks.

And how do I do that? I can't find it in settings.

[bio12]

Disabling "Video Background Play Fix" works. Thanks.

And how do I do that? I can't find it in settings.

Go to the Addons and choose manage addons. Click on the addon "video backplay play fix" and deactivate.

[likecrashingwaves]

Also occurs on Samsung Galaxy S20 FE. Makes Firefox utterly unusable in the current state. There doesn't appear to be a consistent trigger for it either, at least that I can see.

[rvandermeulen]

Is this reproducible on Firefox Beta 98?

[tabrown4]

Behavior confirmed on Google Pixel 4a
Android 12

FF
97.1.0 (Build #2015860771), 365e9fb+
AC: 97.0.10, d6ce171289
GV: 97.0-20220131171509
AS: 87.1.0

Add ons:
ublock origin

[rvandermeulen]

I don't think we need more "me too" comments for 97.1.0. We know the bug is there. What would be helpful would be more confirmation that v98 currently on Beta (or v99 on Nightly) is working as expected to give us more confidence that the fix we plan to ship in 97.2.0 in the next day or so will resolve the issue.

…

On Wed, Feb 16, 2022 at 1:57 PM tabrown4 ***@***.***> wrote: Behavior confirmed on Google Pixel 4a Android 12 FF 97.1.0 (Build #2015860771), 365e9fb <365e9fb> + AC: 97.0.10, d6ce171289 GV: 97.0-20220131171509 AS: 87.1.0 Add ons: ublock origin — Reply to this email directly, view it on GitHub <#23705 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA353PZGYVGB3WJACMKCMZ3U3PXRXANCNFSM5OHTLJCQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

[erikhubers]

I don't think we need more "me too" comments for 97.1.0. We know the bug is there. What would be helpful would be more confirmation that v98 currently on Beta (or v99 on Nightly) is working as expected to give us more confidence that the fix we plan to ship in 97.2.0 in the next day or so will resolve the issue.
…
On Wed, Feb 16, 2022 at 1:57 PM tabrown4 @.> wrote: Behavior confirmed on Google Pixel 4a Android 12 FF 97.1.0 (Build #2015860771), 365e9fb <365e9fb> + AC: 97.0.10, d6ce171289 GV: 97.0-20220131171509 AS: 87.1.0 Add ons: ublock origin — Reply to this email directly, view it on GitHub <#23705 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA353PZGYVGB3WJACMKCMZ3U3PXRXANCNFSM5OHTLJCQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you commented.Message ID: @.>

I've been casually browsing on the couch for almost an hour now with the Nightly and haven't seen it happen yet. All working properly with the Nightly it seems.

99.0a1 (Build #2015862891), 2fee285f7+
AC: 99.0.20220211143103, f62e501d67
GV: 99.0a1-20220211094209
AS: 91.0.1

[likecrashingwaves]

Spent an hour in the beta, and didn't run into any issues. Fingers crossed that's a positive sign?

[rvandermeulen]

FYI, we've started the gradual rollout of 97.2.0. Should be fully available by tomorrow if all goes well with that.

[erikhubers]

Got the 97.2.0 update, issue has not surfaced after one hour of browsing. It seems fixed 🎉

[tomdol]

Updating to 97.2.0 makes it go away, thanks!