Why can’t the devs have it update in the background or on next startup? I was in the middle of my work when I got this. Now I need to close everything and go through all the logins and 2FA again. 😡

Chrome is much better at this, hands down. It has never interrupted me the way Firefox does during updates.

  • Hanrahan@slrpnk.netEnglish
    2·
    8 months ago

    Yeah, caught out the first.time. Now I never OK the update until I am about to close.down, which is a bulahit workaround but there it is. Why can’t it be downloaded with a pop uo notification saying install the update now or wait until you reboot?

  • dubs@lemm.ee
    1·
    11 months ago

    I use it on both Windows and Mac, I’ve never seen this o.o

  • KiranWells@pawb.social
    1·
    11 months ago

    For anyone who is still confused about what causes this: Firefox launches copies of itself when creating new website instances (usually when loading a website that has not already been loaded). Because of this, if it is updated in the background (through any means; I usually see this after a manual system update), Firefox has to restart when you try and load a new site because it cannot create any compatible copies of itself, since the old version is the one that is still running and the copies would use the new (updated) version.

    The solution is to only update when Firefox is closed, or restart it when it asks.

  • Psythik@lemmy.world
    1·
    11 months ago

    I’ve been using Firefox since 1.0PR and I’ve never seen this message before. For me, Firefox has always quietly downloaded the update in the background and then installed it the next time I used it.

    I’m curious to know just exactly what it is you’re doing to make this message come up.

    • PrettyLights@lemmy.world
      1·
      11 months ago

      I saw this yesterday on Linux after a typical update command and it surprised me. Restarting FF reopened all my tabs without issue and it wasn’t really an inconvenience to me.