Back button sometimes goes to the wrong page in Nightly
Categories
(Core :: DOM: Navigation, defect, P2)
Tracking
()
People
(Reporter: jrmuizel, Assigned: smaug)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression, Whiteboard: fission-hard-blocker)
Attachments
(1 file)
I had a situation where the following happened:
- start on https://news.ycombinator.com/
- click on link to: https://inews.co.uk/news/real-life/this-leeds-dad-makes-teddies-with-health-conditions-to-help-children-living-with-medical-disorders-1148392
- hit back button (returns to https://news.ycombinator.com/)
- click on link to https://news.ycombinator.com/item?id=28168933
- hit back button (returns to https://inews.co.uk/news/real-life/this-leeds-dad-makes-teddies-with-health-conditions-to-help-children-living-with-medical-disorders-1148392 instead of https://news.ycombinator.com/)
I was able to reproduce this a couple of times in a row, but can't anymore.
I believe I've noticed this kind of thing happening before, but this was the first time I was able to reproduce it to confirm it wasn't confusion on my part.
Assignee | ||
Comment 1•3 years ago
|
||
Which version of Firefox are you using, and is Fission enabled?
Reporter | ||
Comment 2•3 years ago
|
||
93.0a1 (2021-08-12) and Fission is enabled
Assignee | ||
Comment 3•3 years ago
|
||
This sounds like the issue jesup has seen.
I wish there was some way to reproduce.
Reporter | ||
Comment 4•3 years ago
|
||
Is there something I should check for if it happens again?
Assignee | ||
Comment 5•3 years ago
|
||
Running the script from http://mozilla.pettay.fi/moztests/shistory.log.txt in the browser console when the problematic page is in the foreground tab might reveal something.
Feel free to send the output to me, if you don't want to attach it to this bug.
The output looks something like
index: 1
requestedIndex: -1
count: 2
Entry[0], originalURI: null, uri: about:newtab, ID: 4697
Entry[1], originalURI: null, uri: http://mozilla.pettay.fi/moztests/shisto..., ID: 4833
Updated•3 years ago
|
Comment 6•3 years ago
|
||
Jeff or Randell, have you seen this Back button bug recently?
I haven't been able to repro.
Reporter | ||
Comment 7•3 years ago
|
||
No, but I don't see it/notice it often enough to say that it's been fixed.
Comment 8•3 years ago
|
||
Olli, Randell says he still see this Back button bug "every few days". Nika says this bug is important.
I'm tentatively assigning this bug to you. If you think someone else should investigate, let me know.
Assignee | ||
Comment 9•3 years ago
|
||
jesup, could you send the relevant session history state when you see this (see comment 5).
Updated•3 years ago
|
Comment 12•3 years ago
|
||
From Bug 1731013 Comment 3. This is regressed by Bug 1697905
Updated•3 years ago
|
Assignee | ||
Comment 13•3 years ago
|
||
Using requestedIndex on the child side is hard, because there are race conditions when a session history load is triggered
and at the same time a non-session history load commits a new active entry.
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Comment 14•3 years ago
|
||
Comment 15•3 years ago
|
||
bugherder |
Comment 16•5 months ago
|
||
This was fixed on the Latest Nightly build 132.0a1 verified on platforms: Windows 10, macOS 12 and Ubuntu 22.04 using the steps from description.
Comment 17•5 months ago
|
||
Verified as fixed on Android as well , on the latest Nightly 132.0a1 from 05.09.2024 using Samsung Galaxy S23 Ultra (Android 14).
Description
•