Forum Discussion
Interesting. Mine says it is still 78.0.249.1, and I wasn't aware of it updating. BUT I now have the favourites button, which I didn't before yesterday in 78.0.249.1, and a working Share button ... which only appears to share using Microsoft Windows 10 Apps, not e.g. the email client I actually use and have set as the default email program. It's as if the update silently happened at least in part but didn't change the version number within the program.
But still no middle-click on a favourite opening it in a background tab but leaving the favourites menu (and sub-menus) open for further clicks on more favourites. (And yes I'm going to mention that in my reaction to every release until that's added to Edge, or - as with Google Chrome - you say you're not going to do it or I conclude you're not ever going to do it and I uninstall Edge.)
- AnthonyAug 30, 2019Steel Contributor
XX.X.XXX.1 can usually mean a minor revision fix like a bug or crashing issue. Google does it with their Canary. You'll see something like 78.0.3896.4 and you had 4 updates of 3896 (.4) that day. You may or may not even notice the reason for it. It could be mean anything but I usually found or saw it was logged as having to do with something like a bug or crashing bug or a possibly security weakness. That it called for an update of that version right away instead of the usual next day, week, month, and so on. For example lets say Canary (or Dev) comes out at 9 AM and everyone is complaining it's crashing on launch or this feature is giving them an error and the browser is completely unstable...the developers see it and know it's a must do fix to get the browser working again today or this week...they fix it right away...maybe even twice in one hour, and released the minor updates that is now a "1." or ".2" like 78.0.2XX.2. Instead of 78.0.2XX.0. Google Canary was doing that a few days ago with their Canary that it went up too .3 (I had three updates that date...I've seen go as far as .8) within two hours and the first two updates of that day were causing hanging or crashing of the browser.
Chromium itself (not Chrome) has one build released each day. Like today it's 78.0.3897.0 but it can have up to 40 revisions of that day's build a day by different developers (Chromium doesn't have an auto-updater unless you write a script or batch file and even then it doesn't always work...so it has to be manually downloaded/installed with each new build/revision). However Chromium is the "off the trunk" version that usually will be promoted to Chrome's next day Canary version and can be buggy and unstable as heck (even throughout the day). Example being on that specific day Chromium might be at 78.0.3896.X while Chrome Canary was updated that same morning too 78.0.3897.X. (I'm not sure how Edge is doing it with their Canary such if they're working with the latest day's build of Chromium and promoting it up to their Edge or instead have their own thing going on). Google uses an autobot system that uploaded/updates the Canary browser each day.
- DavidGBAug 30, 2019Steel Contributor
I know. My point was that the version number of Edge Dev on my laptop never changed, including the final .1. I had Edge sitting there on the Settings>About page, refreshing it every now and then looking for the expected weekly update, but it never showed itself doing an update, and at some point the favourites address bar button and the Share menu entry appeared that were supposed to come with the update from 78.0.249.1 to 256.2, even though I never saw an update indicated and the version number remained the same after as it was before. Which is odd.
- AnthonyAug 30, 2019Steel Contributor
I'm not on Dev, so I'm not sure what build their on right now. Canary is pretty stable enough for me that I use that as my priority browser....if that becomes unstable (which has been almost no existent for me) I jump onto Chromium or lastly Chrome Canary and of course I still have the old Edge. That problem you mention could be a glitch or an error of updating the revised number or they simply corrected the issues at hand but kept it under the same build number. I don't know have Edge is working their uploads and build revisions. Good thing is Dev comes out once a week so whatever didn't show up or work out might (or will) in the next week version and one can always use Canary.