7 ms·

Oh cool! Now that I think of it I haven't seen the crash window in quite some time. Well done! Now if I could only disable Ctrl+Q and prevent it from asking fo

Oh cool! Now that I think of it I haven't seen the crash window in quite some time. Well done! Now if I could only disable Ctrl+Q and prevent it from asking for a restart after update...

MawKKe 5y ago
It does not really ask, it straight up bricks the whole browser session until you do. But otherwise, FF has been really stable for years now
Vinnl 5y ago
I haven't been able to disable it, but the option "Warn you when quitting the browser" at the top of preferences has already saved me numerous times. Not as perfect as disabling, but far better than nothing.
- cpeterso 5y ago
  There is a new "browser.quitShortcut.disabled" setting in about:config to disable Ctrl+Q.
deadbunny 5y ago
I've never really had an issue with restarting Firefox, it remembers all my tabs when I restart it either after an update or just a close/open. Perhaps it's a setting I toggled years ago and have since forgotten but I'm not sure what the complaint is about restarting after an update?
- Abishek_Muthian 5y ago
  Unless there's a private window, which gets lost during these forced restart after updates.
- randlet 5y ago
  At least for me after FF updates itself it won't let you open a new tab or anything until it restarts. According to this Reddit post this is due to it being updated by the package manger so maybe it's a Linux only issue?: https://old.reddit.com/r/firefox/comments/jwx54y/firefox_forcing_to_restart/ https://old.reddit.com/r/firefox/comments/jwx54y/firefox_for...
  - lazulicurio 5y ago
    It's due to the "unattended upgrades" feature. You can blacklist FF from getting those upgrades with a change to /etc/apt/apt.conf.d/50unattended-upgrades. Add "firefox" to the "Unattended-Upgrade::Package-Blacklist" section. I find manually upgrading much less annoying than having my browser randomly lock up on me.
    - randlet 5y ago
      Thank you!
- input_sh 5y ago
  It remembers the tabs, but it loses my vertical position within the tabs. When reading articles or a thread on some forum, that's quite annoying. Even Pocket doesn't save my progress on a desktop but does on my phone. It's nothing that would make me stop using it, just an annoyance that I wish I didn't have to deal with on a semi-regular basis.
tux3 5y ago
>Now if I could only disable Ctrl+Q Good news! =) Set browser.quitShortcut.disabled in about:config
- amlib 5y ago
  Since when was that added? Anyway, my days of closing the whole damn browser instead of a single tab are finally over!
  - input_sh 5y ago
    Yeah this must be new-ish. I remember searching for this and only finding some plugins that didn't work on Linux.
    - sylvestre 5y ago
      Indeed, 3 months ago: https://bugzilla.mozilla.org/show_bug.cgi?id=52821#c319 https://bugzilla.mozilla.org/show_bug.cgi?id=52821#c319
  - deleted 5y ago
    [deleted]
  - deleted 5y ago
    [deleted]
- kevincox 5y ago
  I would absolutely love a shortcut manager for Firefox. For example I use this shortcut enough that something like Ctrl+Shift+Q would be useful. (And the dozens of other things that I would like to rebind, including custom shortcuts).
  - Dunedan 5y ago
    I second that. I'd love to be able to configure a shortcut to move tabs to new windows.
- darkwater 5y ago
kevincox 5y ago
> prevent it from asking for a restart after update This isn't just nagging. The API between the main browser context and content processes isn't stable between builds. This means that Firefox can't spin up a new content process if the update has replaced the executable with a different version. Therefore Firefox has the tough choice of trying anyways and risking misbehaviour (including possibly security bugs) or forcing the user to restart the browser process so that it can spawn new content processes. It also depends on how your distribution updates Firefox. For most distributions they have this problem, however NixOS doesn't because the new version is installed in a new directory. IIUC Firefox's self-updater also doesn't have this issue, and I think it supports Linux.
- the8472 5y ago
  > This means that Firefox can't spin up a new content process if the update has replaced the executable with a different version. Couldn't it spin up another one from the old version by doing execve("/proc/self/exe", ...)? Or by keeping a template process around with all the libraries loaded from which a child process can then be forked.
  - dblohm7 5y ago
    Completely possible, but that's not how it works ATM. EDIT: And at the risk of stating the obvious, the fact that it doesn't work this way should be a hint that there are complexities involved that make it more complicated than "just" doing it.
    - phendrenad2 5y ago
      I don't agree. The fact that it doesn't work is not necessarily a hint that there are complexities involved. There are a myriad of other possible reasons, such as no one really cares that Firefox forces you to restart the app whenever it updates. People just get used to it.
      - kaba0 5y ago
reidrac 5y ago
Coincidentally, I have experienced 4 crashes already since 88.0.1 was released. But I agree with you, I can't remember when was the last time I had a crash before these!
kelnos 5y ago
Per a sibling comment, browser.quitShortcut.disabled in about:config works. For me, I just never disabled the option to ask before quitting when more than one tab is open, so that dialog always catches me before I quit by accident.
- coldpie 5y ago
  Sadly it's not enough. If I have one tab open, I still don't want ctrl-q to kill Firefox; and it doesn't count pinned tabs as open tabs, so it will still kill even if you have several pinned tabs open. It's a really, really dumb shortcut to have on by default and I'm thrilled it's finally dead.

Oh cool! Now that I think of it I haven't seen the crash window in quite some time. Well done! Now if I could only disable Ctrl+Q and prevent it from asking for a restart after update...

MawKKe 5y ago

It does not really ask, it straight up bricks the whole browser session until you do. But otherwise, FF has been really stable for years now

Vinnl 5y ago

I haven't been able to disable it, but the option "Warn you when quitting the browser" at the top of preferences has already saved me numerous times. Not as perfect as disabling, but far better than nothing.

cpeterso 5y ago
There is a new "browser.quitShortcut.disabled" setting in about:config to disable Ctrl+Q.

deadbunny 5y ago

I've never really had an issue with restarting Firefox, it remembers all my tabs when I restart it either after an update or just a close/open. Perhaps it's a setting I toggled years ago and have since forgotten but I'm not sure what the complaint is about restarting after an update?

Abishek_Muthian 5y ago
Unless there's a private window, which gets lost during these forced restart after updates.
randlet 5y ago
At least for me after FF updates itself it won't let you open a new tab or anything until it restarts. According to this Reddit post this is due to it being updated by the package manger so maybe it's a Linux only issue?: https://old.reddit.com/r/firefox/comments/jwx54y/firefox_forcing_to_restart/ https://old.reddit.com/r/firefox/comments/jwx54y/firefox_for...
- lazulicurio 5y ago
  It's due to the "unattended upgrades" feature. You can blacklist FF from getting those upgrades with a change to /etc/apt/apt.conf.d/50unattended-upgrades. Add "firefox" to the "Unattended-Upgrade::Package-Blacklist" section. I find manually upgrading much less annoying than having my browser randomly lock up on me.
  - randlet 5y ago
    Thank you!
input_sh 5y ago
It remembers the tabs, but it loses my vertical position within the tabs. When reading articles or a thread on some forum, that's quite annoying. Even Pocket doesn't save my progress on a desktop but does on my phone. It's nothing that would make me stop using it, just an annoyance that I wish I didn't have to deal with on a semi-regular basis.

tux3 5y ago

>Now if I could only disable Ctrl+Q Good news! =) Set browser.quitShortcut.disabled in about:config

amlib 5y ago
Since when was that added? Anyway, my days of closing the whole damn browser instead of a single tab are finally over!
- input_sh 5y ago
  Yeah this must be new-ish. I remember searching for this and only finding some plugins that didn't work on Linux.
  - sylvestre 5y ago
    Indeed, 3 months ago: https://bugzilla.mozilla.org/show_bug.cgi?id=52821#c319 https://bugzilla.mozilla.org/show_bug.cgi?id=52821#c319
- deleted 5y ago
  [deleted]
- deleted 5y ago
  [deleted]
kevincox 5y ago
I would absolutely love a shortcut manager for Firefox. For example I use this shortcut enough that something like Ctrl+Shift+Q would be useful. (And the dozens of other things that I would like to rebind, including custom shortcuts).
- Dunedan 5y ago
  I second that. I'd love to be able to configure a shortcut to move tabs to new windows.
darkwater 5y ago

kevincox 5y ago

> prevent it from asking for a restart after update This isn't just nagging. The API between the main browser context and content processes isn't stable between builds. This means that Firefox can't spin up a new content process if the update has replaced the executable with a different version. Therefore Firefox has the tough choice of trying anyways and risking misbehaviour (including possibly security bugs) or forcing the user to restart the browser process so that it can spawn new content processes. It also depends on how your distribution updates Firefox. For most distributions they have this problem, however NixOS doesn't because the new version is installed in a new directory. IIUC Firefox's self-updater also doesn't have this issue, and I think it supports Linux.

the8472 5y ago
> This means that Firefox can't spin up a new content process if the update has replaced the executable with a different version. Couldn't it spin up another one from the old version by doing execve("/proc/self/exe", ...)? Or by keeping a template process around with all the libraries loaded from which a child process can then be forked.
- dblohm7 5y ago
  Completely possible, but that's not how it works ATM. EDIT: And at the risk of stating the obvious, the fact that it doesn't work this way should be a hint that there are complexities involved that make it more complicated than "just" doing it.
  - phendrenad2 5y ago
    I don't agree. The fact that it doesn't work is not necessarily a hint that there are complexities involved. There are a myriad of other possible reasons, such as no one really cares that Firefox forces you to restart the app whenever it updates. People just get used to it.
    - kaba0 5y ago

reidrac 5y ago

Coincidentally, I have experienced 4 crashes already since 88.0.1 was released. But I agree with you, I can't remember when was the last time I had a crash before these!

kelnos 5y ago

Per a sibling comment, browser.quitShortcut.disabled in about:config works. For me, I just never disabled the option to ask before quitting when more than one tab is open, so that dialog always catches me before I quit by accident.

coldpie 5y ago
Sadly it's not enough. If I have one tab open, I still don't want ctrl-q to kill Firefox; and it doesn't count pinned tabs as open tabs, so it will still kill even if you have several pinned tabs open. It's a really, really dumb shortcut to have on by default and I'm thrilled it's finally dead.