Forum Discussion
*UPDATED* Dev channel update to 78.0.262.0 is live
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.
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.
DavidGB sorry to confuse you with those features popping up unexpectedly! Both of the features you mentioned were actually under a controlled feature rollout, which means they've already existed in the build for a while, but are turned off by default. Then, we can turn them on progressively and you'll just see them magically turn up the next time you open the browser, or you can turn them on manually by finding the right feature flag and enabling it. In this case, all of the features you mention had their rollout bumped up to 100%, which is both why you finally saw them, as well as why I mentioned them in the release notes, even though some people in both Dev and Canary have been seeing them for a few weeks now as the rollout has been progressing.
Even with the latest version of the Dev Edge its not possible to view conteent on https://www.tvnow.de/
After Ads you get a black screen or an infor about DRM Protection from the site. In normal Edge its working fine. The interesting is until begining of August it was working fine with Edge Dev :§
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.
It's happened again!
Edge Dev has been running, but underneath several other program windows I was actually using like Thunderbird and Firefox (which I use for normal browsing because Edge Dev doesn't keep the menu open when I middle click on favourites in favourite menus). Just brought Edge Dev to the front of the window stack, and some time since I posted before a 'Global Media Controls' button has appeared on the Address bar to the left of the Favourite button. That was NOT there earlier, but the version number still hasn't changed from what it has been for the last week. So that's at least two different silent updates that have happened today, with no indication of an update and no change in version number.
You can try uninstalling and reinstalling to see if everything that appear is still there or install on a second computer and compare. I know MS (like Google) has an auto updater. It's running in the background of your task scheduler and usually does a daily check if not hourly and it silently uploads any new updates. Maybe that can be it. Here is a picture from mine. "GoogleUpdateTaskUser" is Googles. MicrosoftEdgeTaskUpdateTaskUser is there and it describes that it does:
