Closed Bug 1825007 Opened 2 years ago Closed 2 years ago

Can’t go back with “about” pages when fission.autostart is set to false

Categories

(Core :: DOM: Navigation, defect)

Firefox 113
defect

Tracking

()

RESOLVED WONTFIX

People

(Reporter: dr2017, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/111.0

Steps to reproduce:

Went to bookmarked “about” pages, for example:

about:addons
about:config
about:preferences

Actual results:

When attempting to go back to the previous page the first time in a newly opened tab it responds. However, if you visit an about page the second time in that tab it will not. This is the case if you use the back toolbar button. the keyboard backspace, or the dropdown list from the forward or back button.

Expected results:

It should have reverted to a previous page, no matter the back method used. When fission.autostart is set to true, it responds properly.

This was tested in a new profile with the same results in both Windows 7 and 10.

The Bugbug bot thinks this bug should belong to the 'Core::DOM: Navigation' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → DOM: Navigation
Product: Firefox → Core

I can't reproduce the problem on Android, which is the only remaining platform where Fission isn't on by default.

Setting fission.autostart to false is not a supported configuration on desktop. Why do you need to set it?

Flags: needinfo?(dr2017)

Mainly because of more processes running and a bit higher memory usage. I keep content process limit at 1 but that is disabled with fission.autostart - true. I didn't know this was no longer supported on desktop when false otherwise the bug wouldn't have been filed but thanks anyway.

Flags: needinfo?(dr2017)

Thanks. Given that this doesn't repro on Android and the desktop configuration is unsupported, I'm closing this.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.