Firefox unable to navigate back on certain pages
Categories
(Core :: DOM: Navigation, defect)
Tracking
()
People
(Reporter: mozillabz, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: parity-safari)
Attachments
(1 file)
259.90 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:95.0) Gecko/20100101 Firefox/95.0
Steps to reproduce:
Reproduce with 95.0.2 on different OSs:
- visit https://bugs.documentfoundation.org/page.cgi?id=weekly-bug-summary.html
- click any of the opened / closed in last 7 days numbers to go to that page
- once page has loaded press back arrow or cmd left to go back to previous page
Actual results:
Firefox stays on the page and never goes back. this is a new behavior as navigation has worked as expected in the past.
Expected results:
Firefox should navigate to the initial page it was coming from.
Navigation works as expected when using Safari or Brave so this certainly feels like a problem in Firefox.
Right-clicking the back arrow shows there is one more page loaded between the overview page and the page listing the individual bugs. That might be unexpected behavior by bugzilla, but since navigation works fine in Safari and Brave it should be solvable for Firefox as well.
It's the same when trying to navigate back from Bugzilla search results to the search page.
FF 95.0.2 (64-bit) Arch Linux
Comment 2•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::Address Bar' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Updated•2 years ago
|
Comment 3•2 years ago
|
||
I could not reproduce with Fission disabled.
I ran mozregression with Fission enabled and got,
40:32.73 INFO: Last good revision: c25899d7b631470b983650ee254177381a62eaad (2020-10-02)
40:32.73 INFO: First bad revision: 33139800aca52aac192973fe24c9b74df7c87e00 (2020-10-03)
40:32.73 INFO: Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=c25899d7b631470b983650ee254177381a62eaad&tochange=33139800aca52aac192973fe24c9b74df7c87e00
It seems not a recent regression, but a bug existed since we enabled SHIP with Fission.
Peter or Olli might have an idea of what is going wrong.
Comment 4•2 years ago
|
||
This is possibly a dup of bug 1747033
Updated•2 years ago
|
Updated•2 years ago
|
Description
•