1954845 - The history tab is not displayed when long-pressing on system back button on Android 15 on Pixel devices

Status: RESOLVED INVALID

(Firefox for Android :: History, defect)

Description

[Daniel]

Steps to reproduce

1. Navigate to a website
2. Open several links in the same tab
3. Long-press the Android back button.

Expected behavior

The history panel shows up displaying the tab history.

Actual behavior

There is no history panel displayed.

Device information

FIrefox Stable 136.0.1
Firefox Beta 137
Google Pixel 6 XL with Android 15, March update, NovaLauncher latest beta (I think). Also affects stock launcher.

Any additional information?

This is a 'duplicate' issue for Bug 1944817, because I'm still affected by it.

Comment 1

[Vasilica Tamas (Android QA) [:vtamas]]

Attachment: Android15BackButton.mp4

I was able to reproduce this issue on Firefox Nightly 138 (2025-03-27) and Firefox 137 using Google Pixel 8 (Android 15). Nothing happens when long-pressing the Android back button and I confirm that this issue has started only after the Android update from March 5, 2025.

Comment 2

[Daniel]

(In reply to Vasilica Tamas QA [:vtamas] from comment #1)

Created attachment 9475074 [details]
Android15BackButton.mp4

I was able to reproduce this issue on Firefox Nightly 138 (2025-03-27) and Firefox 137 using Google Pixel 8 (Android 15). Nothing happens when long-pressing the Android back button and I confirm that this issue has started only after the Android update from March 5, 2025.

Oh thank god, I'm glad I'm not losing my marbles!

Comment 3

[Bob]

Based on https://bugzilla.mozilla.org/show_bug.cgi?id=1946778#c15, it is unlikely that reverting to old behaviour would help at all.

I have attempted to report this to Google via the Android bugtracker. Hopefully they can do something, I don't think we have any options here. https://issuetracker.google.com/u/1/issues/408373116

Comment 4

[dalgoda+github]

tl;dr: It works for me on Pixel Pro 6, but with a delay. Trying with waiting 10s after visiting a page, it seems to always work as expected.

I have two devices: Pixel Pro 6 running Android 15. (I work at G and happen to be running a prerelease version of A15, but too far ahead). A Blu G93 running A13 March update. (I have an older device running A10 somewhere, but it seems to be buried under junk on my desk).

I have all of the browsers configured to automatically start in Private browsing and a blank home screen. Systems are configured with the system level 3-button navigation (or whatever the name of the day is).

My test consists of:

1. Fresh restart of browser
2. Kebab-menu -> Help (takes to support.mozilla.org)
3. Visit first link in the bottom left card (putting two links in the history)
4. Long press on system back menu
5. Press system back to dismiss the history list
6. Long press a second time to bring up history list
7. Dismiss history list
8. Visit a third page (usually the privacy notice as an easy link to click on)
9. Repeat long press

• 137.0
  • Both systems work as expected.
• 138.0b3 (beta)
  • On BOTH systems:
    • First long press on causes FF to dim, then about five seconds later.
    • Second long press has instant results.
    • After visiting the third page, the third long press has instant results, but WRONG! Initially it is missing the current page, but after about five to seven seconds, it gets updated with the current page.
• 139.0a1 (nightly)
  • On A13, history list is instant and correct.
  • On A15, same experience as 138.0b3.

After noticing the delays, I did some more testing focused on that:

• For all instances where there is a delay after immediately visiting a page, if I wait some amount of time (say ten seconds, just to be sure), then results are instant and correct.
• For all instances where there is a delay, is also affects the highlighted "current" page in the history list. That is, visit three pages, get a good history list, back a page, bring up the history list again, the wrong page is highlighted, but corrects after a few seconds.
• Using the app back button seems to always be instant and correct (did not test as thoroughly).

Comment 5

[dalgoda+github]

I've been using Android since the G1, and finally figured out how to screen cap a video, including touches. Alas, too big to attach so:
https://photos.app.goo.gl/ensJPGBhNMskgi4z8 (private friendly)

Comment 6

[Jackson Sul]

I'm using Firefox 137.0 on a Pixel 8a running Android 15 (March update) and experience the same problem, no history tab is displayed on long press of the back button.

I followed Dalgoda's steps above exactly to see if it would show up after a delay, but no, no history menu ever appears for me, with or without a delay.

Comment 7

[Jono]

Having this issue on Pixel 7. History never shows up, regardless of how long I'm on the page.

Have tested with current stable, beta, and nightly.

Also tested with 134, same issue.

Comment 8

[Bob]

Would anyone here with a Pixel device be willing to capture an Android bug report as per Google's request over at https://issuetracker.google.com/u/1/issues/408373116#comment3?

Comment 9

[Jono]

Bob,

I would love to help. Unfortunately I don't have access to the Drive link you shared over on the Google site. Can you give me access, or provide a summary of what you need me to capture in the bug report?

(not sure how to share my Gmail address privately here)

Comment 10

[Bob]

(In reply to Jono from comment #9)

Bob,

I would love to help. Unfortunately I don't have access to the Drive link you shared over on the Google site. Can you give me access, or provide a summary of what you need me to capture in the bug report?

(not sure how to share my Gmail address privately here)

What we need is someone to 'reproduce' the issue (i.e. attempt and fail to long-press back), then capture an Android bugreport and share via their own Drive link as per the Google team member's instructions on the linked bugtracker:

Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer: https://developer.android.com/studio/debug/bug-report#bugreportdevice

Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.

Note: Please upload the bug report to google drive and share the folder to [e-mail], then share the link here.

Please ignore the existing link I have there - it was from someone else I asked to capture one since I do not own a Pixel device.

To be quite honest I don't think the report will be particularly useful but they've requested it before investigating further. This bug report should be going directly to Google - no one here, Mozilla or otherwise, will be able to see it. If you are able to, please post it directly to the Google bugtracker.

Thank you!

Comment 11

[Jono]

Well. Something in the system is detecting long presses, because I do get a tactile response (distinct from the tactile response for short taps).

Appears I misread your comment, all clear now. I shared a bug report to the Google thread, guess we let them take it from here.

Thanks for your work on this!

Comment 12

[Bob]

The Google issue has been closed as fixed, with this comment:

The issue has been fixed and please watch out for future releases.

At the moment there's no indication of what "future releases" necessarily means but if anyone is able to test a Pixel device with the May update or perhaps the June one next month that would be appreciated.

Comment 13

[Jackson Sul]

I have the May 5, 2025 Android 15 update on a Pixel 8a. Tested with Firefox 138.0.3, still broken unfortunately. Maybe it'll be fixed in June.

Comment 14

[Daniel]

As of the June Android update, this has been fixed, huzzah!