1889135 - Can not navigate back using the back button when performing a search at ny.gov

Status: NEW

(Web Compatibility :: Site Reports, defect, P2)

Description

[Raul Bucata]

Attachment: 20240402_171807.mp4

Environment:
Operating system: Android 12/ Android 13
Firefox version: Firefox Nightly 126.0a1 (2016012423-🦎126.0a1-20240331204101🦎)

Preconditions:
Clean profile

Steps to reproduce:

1. Navigate to : https://www.ny.gov/
2. Tap on the drop down arrow menu located in the page header.
3. Tap inside the search field and perform a search.
4. Once the search result page is opened, tap on the "Back" button (device or browser) .
5. Observe the result.

Expected Behavior:
Navigation to the previous page is performed

Actual Behavior:
Redirect to the same page is performed, without going back

Notes:

• Reproducible regardless of the status of ETP
• Reproducible on the latest build of Firefox Nightly and Release
• Works as expected using Chrome
• Attachment provided
• Issue found during WebCompat team [Top100] websites testing
• Generally speaking, Release and Chrome are showing a different result page

Comment 1

[Donal Meehan [:dmeehan]]

Raul, I can repro this also on Fx125 beta but not in Fx124.
Hopefully, you or Android QA could provide a regressor?

Comment 2

[Raul Bucata]

Hi Donal. I've managed to peform a mozregression via GUI, using gve build. Results:

• Bug 1881620 - enable media engine for encypted playback on Nightly and Dev Edition. r=media-playback-reviewers,padenot
• Differential Revision: https://phabricator.services.mozilla.com/D202511

Comment 3

[Jeff Muizelaar [:jrmuizel]]

Raul, can you rerun the regression window? Bug 1881620 doesn't seem particularly likely.

Comment 4

[Raul Bucata]

Both QA that performed the regression had the same result with GUI. I can also confirm.

Running the mozregression via CMD Windows shows the following:

• Last good revision: d9ad55d66d8523561815b7fbeef13f84428eb55b
• First bad revision: ae0da9180abdc1990832791041b323e05082f6f8
• Pushlog:
  https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=d9ad55d66d8523561815b7fbeef13f84428eb55b&tochange=ae0da9180abdc1990832791041b323e05082f6f8

Notes:
There is a build range that is broken, as another pushlog was seen:

• https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=35c5c892ca1e96f731d20bc6edd310a5d4e13bad&tochange=c4f4e70ebe00262e4bc249e3aafb4e308881a514

As a note, running mozregression via GUI has always been problematic. We will try for future references using CMD via Windows.

Comment 5

[Ryan VanderMeulen [:RyanVM]]

That makes a lot more sense.

Comment 6

[Peter Van der Beken [:peterv]]

Pretty sure this is misdiagnosed, it's a result of bug 1883279. The previous behaviour is relying on a feature that was turned off in general, but accidentally turned on in certain cases on Android. We decided to turn it off always for now, similar to desktop, while the feature is being fixed (see bug 1645211). Also, it was always turned off with session history in the parent on Android, which we're trying to turn on to unblock Fission.

Note that the broken behaviour has always been there on desktop, where the feature was properly disabled (because a number of bugs were discovered).

Comment 7

[Donal Meehan [:dmeehan]]

:peterv what is tracking turning this off for Android? Wondering what the status is for Fx126?

Comment 8

[Peter Van der Beken [:peterv]]

Not sure I understand the question. Bug 1883279 turned off the "back button intervention" completely for Android.

The "back button intervention" was supposed to be turned off on all platforms already because of problems with the implementation. But on Android it was accidentally left turned on in some cases. Turning it off causes the behavior that this bug is filed about. It's the behaviour that we had already on desktop, and it's the behaviour we'll have on Android too now. Once all the problems with the "back button intervention" are fixed we can turn it on again, and this bug will be fixed too. That won't happen for 126, it's tracked in bug 1734181/bug 1645211.

Comment 9

[Donal Meehan [:dmeehan]]

Thanks. This answers my question.

Comment 10

[James Graham [:jgraham]]

So my conclusion here is that this affects all platforms, is an annoyance rather than breakage, and although it was a regression it was an intentional one. We don't specifically need extra diagnosis at this time.