Allow Automatic Update of the Browser
-
@cheve11e_191 This might be OK when the browser is well-seasoned and pretty much always-stable, version after version. The outcry here if some of our versions updated in the background would be considerable. Don't you think? I personally never want that to happen in my case, though some might like the option.
-
@ayespy yeah, I think it would not be a problem with Stable Version (there should be predefined auto-update), and as far as Snapshot is concerned, it would be for users whether they want it or not.
And I have just submitted this proposal because of people who don't how to update a bowser, and then there is a greater risk of using the version with errors.
-
@cheve11e_191 In general, that's probably so - but the update to 1.14 stable, for instance, pissed off a lot of people. I think some others were glad they waited on the update until they had seen some feedback. So - just sayin'...
-
How about delay 24/48hrs silent autoupdate with positive confirmation from early manual update user? That way dev can halt a problematic autoupdate pushing to majority of user if certain amount of early updated user found problem in the update.
Majority of people r not very smart & will only update their browser when "something is wrong" with the browser they r using. Thus most software support silent auto-update to help these users. But when a bad autoupdate broke the software then it will be a big mess for these not so smart user. However, we can minimize the risk of bad silent autoupdate by first releasing the update through notification/manual update (current update method), then initiate silent autoupdate after 24/48hrs if dev team receive no bad report about the update from early updated user.
Personally, i always wait a day or two after received update notification to avoid bad update. I despise silent update because it's unreliable & cause too much trouble when it deliver me a bad update.
-
It just needs another option in Settings, Updates
Download updates automatically and apply on restart -
@dude99 Just optional, I want keep my precious manual updates based on forum feedback ...
-
Best long term solution for this Windows-only consideration would be Store integration.
Unless there is some expectable fineprint for no browsers beside IEdge!. -
-
That ultimately my hopes (Microsoft did not pull that exact d**k move) would be crushed, I understand…
@ayespy but after only 5 minutes of dreaming of a bearable present? -
This might be okay only if it's opt-in and not opt-out. I want to know about the changelog before updating.
-
yeah, please add an opt-in auto update for people dont have a clue how to update a browser
-
@usmave said in Allow automatic update of the browser:
yeah, please add an opt-in auto update for people dont have a clue how to update a browser
The learning curve is extremely low.
-
The updater behaviour could be put in the welcome page:
( ) Always update: applied on vivaldi restart/close; Probably the best choice for stable.
( ) Ask before update: show update window with changelog; Default choice for snapshot; Same of the notify setting checked.
( ) Manual updates: *"check for updates" should be used in this case; it will trigger the update window with changelog; Is the same of notify setting unchecked.
-
It just needs to be opt-in rather than enabled by default. When enabled, I would never want to have to click a button for it to do it, it should just be done automatically without user interaction.
-
@sadetta It shuts off updates as well as notification of available updates. Yes, it is a slight security risk for novice users, but those who choose to disable notifications will check manually for updates from the help menu, or follow the blogs and forums to learn about updates.
For those of us who visit the forums daily, there is no need to enable notification of updates.
-
@sadetta Updates require user intervention. If you turn off notifications, you should check manually from time to time. There is no automated update system that will update your browser without your involvement.
-
@sadetta Notifying you when an update is available IS notifying you about updates. But the latter text is more economical. Were it to tell you when an updated has been applied, it would read "Tell me when a update has been applied."
If you think the text is a bug, please read this linked tutorial and then file a bug report.
-
@Ayespy and how does Chrome achieve that?
-
@SuperRey They have an updater that runs in the background periodically whether Chrome is open or not. Vivaldi will not do that. Note I didn't say Vivaldi couldn't use such a system - simply that they don't. And for the foreseeable future they won't. They want the user in control over whether an update happens or does not.
-
You don't need to run an updater in the background all the time to have automatic updates. Vivaldi could automatically download updates (based on a user setting, and only while the browser is running), and then apply them on the next browser start or exit. It wouldn't be quite as invisible as Chrome's system, but still decent.
Additionally, the update system itself could be enhanced to do most of the unpacking of files and stuff while the browser is still running, so the next start-up only needs to replace the application .exe (doable) and maybe tweak some registry stuff (or whatever else it is Vivaldi does that requires it to be closed during updates). This would reduce the start-up time of the browser after an update significantly as most of the heavy-lifting would already be done. However, I don't know how big of a task it is to re-write the update system, though, so this might not be as feasible as it might first seem.