this post was submitted on 05 Aug 2023
1 points (100.0% liked)

Firefox

12 readers
1 users here now

The latest news and developments on Firefox and Mozilla, a global non-profit that strives to promote openness, innovation and opportunity on the web.

You can subscribe to this community from any Kbin or Lemmy instance:

Related

Rules

While we are not an official Mozilla community, we have adopted the Mozilla Community Participation Guidelines as far as it can be applied to a bin.

Rules

  1. Always be civil and respectful
    Don't be toxic, hostile, or a troll, especially towards Mozilla employees. This includes gratuitous use of profanity.

  2. Don't be a bigot
    No form of bigotry will be tolerated.

  3. Don't post security compromising suggestions
    If you do, include an obvious and clear warning.

  4. Don't post conspiracy theories
    Especially ones about nefarious intentions or funding. If you're concerned: Ask. Please don’t fuel conspiracy thinking here. Don’t try to spread FUD, especially against reliable privacy-enhancing software. Extraordinary claims require extraordinary evidence. Show credible sources.

  5. Don't accuse others of shilling
    Send honest concerns to the moderators and/or admins, and we will investigate.

  6. Do not remove your help posts after they receive replies
    Half the point of asking questions in a public sub is so that everyone can benefit from the answers—which is impossible if you go deleting everything behind yourself once you've gotten yours.

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] growlph@pawb.social 0 points 1 year ago (1 children)

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.

[–] Zagrebian@fedia.io 1 points 1 year ago

Could Firefox not delay the update until the user actually restarts the browser?