Go to about:config - find option browser.tabs.closeWindowWithLastTab - set to false. If you’re only using the close tab button, it will never close out of the program. If you’re closing a lot of windows using the window control though that won’t really help.
It also is very unstable when using multiple profiles. The profiles update individually, so very often you start a second profile and it updates firefox, which makes the first profile not work anymore. You don’t really notice that though, it just stops loading any websites.
Also on mobile it stops streams running in the background after some time, so when listening to something via firefox you have to actively use FF while listening, can’t leave the phone turned to standby
On mobile, I’ve found that switching tabs before switching away from the FF activity mitigates this. Not sure if it’s FF, the website, or Android messing it up, really.
deleted by creator
Seems to be a security feature that is bypassed by a Chrome feature.
Sounds like an OPSEC disaster waiting to happen.
Go to about:config - find option browser.tabs.closeWindowWithLastTab - set to false. If you’re only using the close tab button, it will never close out of the program. If you’re closing a lot of windows using the window control though that won’t really help.
deleted by creator
It also is very unstable when using multiple profiles. The profiles update individually, so very often you start a second profile and it updates firefox, which makes the first profile not work anymore. You don’t really notice that though, it just stops loading any websites.
Also on mobile it stops streams running in the background after some time, so when listening to something via firefox you have to actively use FF while listening, can’t leave the phone turned to standby
On mobile, I’ve found that switching tabs before switching away from the FF activity mitigates this. Not sure if it’s FF, the website, or Android messing it up, really.