Forum Discussion
Dev channel update to 79.0.294.1 is live
Great work on the recent builds Team!
I'm noticing some high CPU usage in the latest build on Mac - my workstation was updated to Catalina last night so not sure if that has anything to do with it.
Also, are there any plans for a dedicated "Check for updates" button on PC like there is in Mac's "Help" menu? Having to go into Help & Feedback > About Edge for manual update checking is quite tedious.
Looking forward to future builds! 🙂
- Spoiler
CIMarketingVideo wrote:Great work on the recent builds Team!
I'm noticing some high CPU usage in the latest build on Mac - my workstation was updated to Catalina last night so not sure if that has anything to do with it.
Also, are there any plans for a dedicated "Check for updates" button on PC like there is in Mac's "Help" menu? Having to go into Help & Feedback > About Edge for manual update checking is quite tedious.
Looking forward to future builds! 🙂
I'd like a dedicated update button as well. the current system is taken from Google chrome without any changes. in the past Microsoft relied on Windows update to ship updates to their browsers (IE and Edge classic), so they should create a new system for the new Edge too, like you said a dedicated button for update.
I also think they should add a setting in GP to let us change the frequency of the auto update checking cycle. like set it to every 30 mins, 1 hour or 24 hrs.
of course the shorter durations are better for Canary.
HotCakeX "I'd like a dedicated update button as well."
What exactly do you mean by this? You want to be able to request it or do you want to be able to stop it?
I only ask because, like Chrome itself, if you go to the About Microsoft Edge menu item, it will check for the most recent update and download if there is one. It's the default action in Chrome and I assume it is in Edge as well.- I want to have a dedicated button so that when I click on it it will check for browser update 🙂
CIMarketingVideo
I'll stick my nose in & say something about the updating for you. Presently, we are updating beta builds, previews, test rats, call the Edge C Channels whatever, but... once with a non-beta, non-Insider Build, it will not be manual or frequent updating. Will be similar to Edge being kept up to date; it will be Edge being kept up to date (wink). Consider, currently, there are 3 (different) Channels and 3 (different) rates of updating; that's no norm in daily practice with an entrenched browser which, Edge C isn't, yet. It's a work in progress, now and won't be manually updating after it's done & kicked out the door.
Cheers,
Drew- Spoiler
Drew1903 wrote:CIMarketingVideo
I'll stick my nose in & say something about the updating for you. Presently, we are updating beta builds, previews, test rats, call the Edge C Channels whatever, but... once with a non-beta, non-Insider Build, it will not be manual or frequent updating. Will be similar to Edge being kept up to date; it will be Edge being kept up to date (wink). Consider, currently, there are 3 (different) Channels and 3 (different) rates of updating; that's no norm in daily practice with an entrenched browser which, Edge C isn't, yet. It's a work in progress, now and won't be manually updating after it's done & kicked out the door.Even when the stable version of Edge will be released, that doesn't stop Beta/Dev/Canary users.
google chrome stable is released but there are still huge number of beta/dev/canary testers for the browse, they range from enthusiasts to developers and anyone in between.
most of us are used to more regular updates and I believe a good amount of people will want to still have faster and sooner access to the new features in Edge insider so they'd keep a Dev/Beta/Canary version beside the Stable version.
so my point is, a dedicated update button and an ability to set update cycle for Edge insider is a good idea. google chrome is missing this feature and it makes it double important for Edge to implement it as an advantage.
