1756731 - it need to back twice to go back to the previous page.

Status: VERIFIED FIXED

(Core :: DOM: Navigation, defect, P3)

Description

[Alice0775 White]

Steps to reproduce

1. Open any web page
2. Open https://www.mozilla.org/ja/firefox/all in the same tab
3. Try to back to previous page

Actual results:
it need to back twice to go back to the previous page.

Expected results:
It should be a single back navigation to go back to the previous page.
Chrome works as expected.

This is not a recent regression.
Setting browser.navigation.requireUserInteraction to true resolve this.

Comment 1

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

First, navigated to https://www.mozilla.org/ja/firefox/all/, but immediately, redirected to https://www.mozilla.org/ja/firefox/all/#product-desktop-release (only anchor changed without scroll). I guess that the first URL shouldn't be treated by the Back button at least.

johannh: Could take a look or just set the priority and severity?

Comment 2

[jscher2000]

A while ago I saw a bug with a reason that browser.navigation.requireUserInteraction had not been defaulted to true but I can't find it now. Is there still a problem with doing that?

Comment 3

[Johann Hofmann [:johannh]]

I'm no longer working on Firefox, so clearing NI :)

Yes, you'll want to get bug 1645211 done, which might resolve this.

Comment 4

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

johannh: Sorry for requesting ni to you, and thank you for the link to bug 1645211.

Alice-san, you set this to a blocker of bug 1515073, did you mean that this is a regression of bug 1515073? If so, this should be marked as so and set this to depending on bug 1645211.

Comment 5

[Alice0775 White]

(In reply to Masayuki Nakano [:masayuki] (he/him)(JST, +0900)(away -8/31) from comment #4)

you set this to a blocker of bug 1515073, did you mean that this is a regression of bug 1515073?
If so, this should be marked as so and set this to depending on bug 1645211.

I think this is not regression. Setting browser.navigation.requireUserInteraction to true will fix this.

Comment 6

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

Thank you, then, I set same priority as bug 1645211.

Comment 7

[Bogdan Maris, Desktop Test Engineering]

This looks fixed to me on the Latest Nightly build 132.0a1 across platforms (Windows 11, macOS 13 and Ubuntu 22.04) after browser.navigation.requireUserInteraction was enabled by default in bug 1734181.

Comment 8

[Adina Petridean QA [:apetridean]]

Verified as fixed on Android, on the latest Nightly 132.0a1 from 11.09.2024 using Samsung Galaxy S23 Ultra (Android 14).