this post was submitted on 22 Apr 2024
826 points (97.8% liked)
memes
10406 readers
1802 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to [email protected]
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads
No advertisements or spam. This is an instance rule and the only way to live.
Sister communities
- [email protected] : Star Trek memes, chat and shitposts
- [email protected] : Lemmy Shitposts, anything and everything goes.
- [email protected] : Linux themed memes
- [email protected] : for those who love comic stories.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I just wish Firefox had a "stay running in the background" option like Chrome so that I didn't have to log back into my Bitwarden vault everytime I accidentally close all of my browser windows.
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.
This did actually help a lot, thanks!
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.