OP here. Most of the comments completely missed the point, but whatever.
deleted by creator
I shared a screenshot, so I was not able to add text to the post. Maybe it’s possible, I don’t know. If there was a text box to add more text to the post, I would have explained the problem.
Good explanation at https://www.reddit.com/r/firefox/comments/x55hon/comment/in09szk.
you’re running multiple profiles of Firefox at the same time (so restarting one with a queued update writes the changes to disk, throwing the other profile instances out of alignment).
In that case, launching a different profile in a new window should not use the new version. In other words, Firefox should not do anything with the pending version until the user actually restarts the entire browser. Having the second window run in the new version just because there was a pending version seems like a bad approach.
Exactly this. I often browse the interwebs while waiting for updates to finish. If Firefox gets updated, it’ll prompt me to restart it.
Not sure ht the big deal is here. 🤷🏻♀️
The problem is that the user should not be prevented from browsing the web just because a new update is ready. The user should choose when to update. If the user has multiple important tabs open, they should be able to finish their work, but if Firefox refuses to load any new tabs, then the user cannot continue working normally.
But if the program isn’t restarted then it could become unstable or crash. You shouldn’t really have any software running while doing updates anyway. I browse the web knowing that I’ll need to restart Firefox so I never do anything of import while waiting.
I’m not “doing updates”. I’m just using Firefox normally.
Is there a missing screenshot here?
Need more info about the running environment.
How do you update software? Package manager?
No, it’ just a macOS application. Firefox updates itself automatically on macOS.
This is actually not unique to Nightly - the stable build does it, too.
I do recognize that scheduling updates is hard - no user ever wants to stop what they’re doing and restart something, and it’s important to keep users from running problematically out of date software.
I agree with OP though that this particular interaction is unusually frustrating for me. This message only appears after trying to load a link or a new tab, meaning it’s actively waiting for me to want to use the browser before telling me that I can’t, essentially guaranteeing it will interrupt my workflow.
I don’t have a good suggestion on how to fix this without making the update system less robust - it might just be a necessary evil - but I do feel that OP’s concern is legitimate.
Could Firefox not delay the update until the user actually restarts the browser?
