Steps to reproduce Fresh install FF. Go to private browsing and open some tabs. Force close the app. Reopen the app and observe tabs tray. Expected behavior Alll tabs (normal and private) are resto...
I almost exclusively use private tabs and had quite a few of them open at any time for things I was working on. But apparently since I’ve last updated the default behavior changed to close private tabs and the option to keep them open was removed.
Digging into it, I’ve found the bug report in the link. The last entry in the bug report is concerning:
It looks like this was discussed in FXIOS-8672, although I don't have access to that JIRA to take a look at the discussion.
I've intentionally kept this PR as simple as possible so we can release it and then be sure there is no major blow back from users. If we need to roll back it should be very simple in the current state.
I'm not sure what would count as "major blow back" but there is at least some hope that this functionality can be restored.
I agree with @garnetred that this behaviour isn't limited to force closing the app.
You could have two different website sessions logged in at the same time using regular and private tabs. This was much more convenient than having to open a different browser. I hope they plan to release container tabs soon.
Not sure why the OP would prefer private tabs though.
On windows, in the run dialog (win+R) type
firefox.exe -p to open the profile wizard.
You can also make custom shortcuts but I don't recall the exact command.
If you sign in with the same Firefox account on both profiles to sync bookmarks and stuff, the only thing different would be what ever you're signed into.
They don’t stay open very long, but I certainly am not expecting them to close just because I haven’t used my phone for a couple hours. At any rate, I want to decide when they close.
I’d consider it a bug if the existing option was removed. Private tabs are nice if I intend to return to the page at a later date. I prefer Firefox Focus for one and done private browsing.
Silently changing a behavior, especially one that is in other web browsers, is a bit user-hostile and I understand the frustration.
On the other hand, privacy-wise this change is good, since it was likely storing the incognito tabs (browser state) in the app storage and was likely retrievable by forensics tools (ie: Cellebrite).
I'd rather have the browser state of incognito tabs stored in RAM at all time.
I feel like those affected are using incognito tabs as a way to separate their browsing history. Maybe a more convenient option would be the ability to run multiple browser sessions on mobile instead of falling back on the incognito mode as a workaround.
They had an option to close the private tabs, which was on by default. I’ve changed it to off for a reason. Breaking people’s workflow for a false perceived gain in privacy is bull. Private tabs are just local storage cleaning tabs. Pretending this change improves privacy is nonsense.
I think this is the behaviour most people expect. Coming back hours later and finding your old private tabs still in the browser seems to defeat the purpose of using private tabs.
You might consider seeing if Container Tabs paired with the Temporary Containers addon serves your need. With that setup, every new tax you open is isolated from the local storage of your other sessions, much like private browsing. You can also set up defined containers for sites you want to remember the state of.