3 ms·

The two things that would get me to consider switching back to Firefox: 1. It not longer forces to restart my entire browser for an update, where every new tab

The two things that would get me to consider switching back to Firefox: 1. It not longer forces to restart my entire browser for an update, where every new tab I open says "restart before you can use your browser." I am not going to use a browser that closes my various windows full of API documentation once a week. I know I can disable auto-updates, but that is also not what I want: it should update when it is finally closed (like Chrome), but not update and then break my browser until I close it. 2. Individual threads can crash without taking the browser down. This feature, individually, is why most people switched and did not look back. As with the problem above. It has been requested since 2008 (http://forums.mozillazine.org/viewtopic.php?f=8&t=890085 http://forums.mozillazine.org/viewtopic.php?f=8&t=890085), and again in 2015 (https://support.mozilla.org/bm/questions/1092836 https://support.mozilla.org/bm/questions/1092836). Really, it's the same thing: closing my entire browser solution is an inhibitive inconvenience in my modern workflow, and Chrome never forces this action. Instead, it does everything it can to keep my tabs alive and usable. I will reconsider Firefox when they integrate this (IMO very obvious and critical) requirement. I don't care if it's faster, or uses less battery---if it regularly forces me to close all my tabs, it's unusable.

dblohm7 6y ago
> It not longer forces to restart my entire browser for an update, where every new tab I open says "restart before you can use your browser." Are you on Linux? My understanding is that the distro packages exacerbate this problem, and it is less of an issue if you use the builds direct from Mozilla.
Mandatum 6y ago
On 1: Your tabs don't re-open after an update? You literally click a button, the browser closes and re-opens those same tabs.
- discardable_dan 6y ago
  I have 60 tabs. Re-opening it is a hassle all on its own.
  - gpvos 6y ago
    Have you really tried? 60 tabs is peanuts for current Firefox.
mccr8 6y ago
Like dblohm7 said, the issue here is when something besides the currently running instance of Firefox does an update. This can happen with the Linux distro packages or if you open Firefox with multiple profiles at the same time. I know it is a big pain, but hopefully this at least helps you understand what is going on. If you choose "restore previous session" under general preferences, then you can at least not lose the set of open tabs when you restart. As for 2, Firefox already does this, and has for about 4 years. Since those comments in 2008 and 2015, Firefox has shipped the Electrolysis project, which makes Firefox multi process. The UI (mostly) runs in a different process, which massively improved UI responsiveness, because janky websites can't interfere with clicking on stuff in the UI. One web site crashing can still cause another web site to crash, if it happens to be in the same process (out of 8) but we're hard at work on the Fission project which will move individual website domains into their own process. Though you can still end up with one instance of Google Docs crashing and taking down another one.
- discardable_dan 6y ago
  > I know it is a big pain, but hopefully this at least helps you understand what is going on. Frankly, and don't take this wrong way, I don't care. I'm working on other problems, and don't want to worry about what my browser is doing. I just want it to work. > If you choose "restore previous session" under general preferences, then you can at least not lose the set of open tabs when you restart. Have you ever tried restarting it with 60 tabs open? It doesn't work on my machine. > As for 2, Firefox already does this, and has for about 4 years. Since those comments in 2008 and 2015, Firefox has shipped the Electrolysis project, which makes Firefox multi process. The UI (mostly) runs in a different process, which massively improved UI responsiveness, because janky websites can't interfere with clicking on stuff in the UI. One web site crashing can still cause another web site to crash, if it happens to be in the same process (out of 8) but we're hard at work on the Fission project which will move individual website domains into their own process. Though you can still end up with one instance of Google Docs crashing and taking down another one. I don't care if it's multithreaded to separate rendering from management for performance purposes. What I care about is keeping my remaining tabs when one crashes. > we're hard at work on the Fission project which will move individual website domains into their own process When this occurs, I will once again consider switching back. Though this means if one API tab breaks, they all do---it's still a massive problem.

dblohm7 6y ago

> It not longer forces to restart my entire browser for an update, where every new tab I open says "restart before you can use your browser." Are you on Linux? My understanding is that the distro packages exacerbate this problem, and it is less of an issue if you use the builds direct from Mozilla.

Mandatum 6y ago

On 1: Your tabs don't re-open after an update? You literally click a button, the browser closes and re-opens those same tabs.

discardable_dan 6y ago
I have 60 tabs. Re-opening it is a hassle all on its own.
- gpvos 6y ago
  Have you really tried? 60 tabs is peanuts for current Firefox.

mccr8 6y ago

Like dblohm7 said, the issue here is when something besides the currently running instance of Firefox does an update. This can happen with the Linux distro packages or if you open Firefox with multiple profiles at the same time. I know it is a big pain, but hopefully this at least helps you understand what is going on. If you choose "restore previous session" under general preferences, then you can at least not lose the set of open tabs when you restart. As for 2, Firefox already does this, and has for about 4 years. Since those comments in 2008 and 2015, Firefox has shipped the Electrolysis project, which makes Firefox multi process. The UI (mostly) runs in a different process, which massively improved UI responsiveness, because janky websites can't interfere with clicking on stuff in the UI. One web site crashing can still cause another web site to crash, if it happens to be in the same process (out of 8) but we're hard at work on the Fission project which will move individual website domains into their own process. Though you can still end up with one instance of Google Docs crashing and taking down another one.

discardable_dan 6y ago
> I know it is a big pain, but hopefully this at least helps you understand what is going on. Frankly, and don't take this wrong way, I don't care. I'm working on other problems, and don't want to worry about what my browser is doing. I just want it to work. > If you choose "restore previous session" under general preferences, then you can at least not lose the set of open tabs when you restart. Have you ever tried restarting it with 60 tabs open? It doesn't work on my machine. > As for 2, Firefox already does this, and has for about 4 years. Since those comments in 2008 and 2015, Firefox has shipped the Electrolysis project, which makes Firefox multi process. The UI (mostly) runs in a different process, which massively improved UI responsiveness, because janky websites can't interfere with clicking on stuff in the UI. One web site crashing can still cause another web site to crash, if it happens to be in the same process (out of 8) but we're hard at work on the Fission project which will move individual website domains into their own process. Though you can still end up with one instance of Google Docs crashing and taking down another one. I don't care if it's multithreaded to separate rendering from management for performance purposes. What I care about is keeping my remaining tabs when one crashes. > we're hard at work on the Fission project which will move individual website domains into their own process When this occurs, I will once again consider switching back. Though this means if one API tab breaks, they all do---it's still a massive problem.