Forum Discussion
Dev channel update to 79.0.309.11 is live
UPDATE: We pushed another update, which now brings the build number to 79.0.309.11.
UPDATE: We just pushed an update, which now brings the build number to 79.0.309.7.
Hello insiders, today we’re releasing build 79.0.309.5 to the Dev Channel! You may notice that this is only one build away from last week’s Dev, and that’s because this is our candidate for our next Beta release, so we want to make sure it’s extra polished before we release it there. However, that also means it’s a pretty light week this week in terms of notable changes.
We do have one known issue right now, where Edge sometimes launches to a blank white window. There are two possible causes. If you launch another window and it’s fine, you shouldn’t ever see the issue again. However, if subsequent windows are also blank, you’ll have to disable Application Guard in order to get Edge back into a working state. We plan on releasing another update later this week in order to get us in sync with Chromium’s Beta, so the fix for that cause should be in the updated build.
- Fixed a crash when logging into the browser.
- Fixed an issue where typing in the address bar sometimes causes the browser to crash.
- Fixed an issue where the browser sometimes crashes after completing the first run experience.
- Fixed a hang during the first run experience.
- Fixed an issue where the theme sometimes changes unexpectedly after the first run experience.
- Fixed some issues with Application Guard windows not successfully opening.
- Disabled hardware acceleration in Application Guard windows to prevent them from hanging on certain machines.
- Fixed an issue where certain webpages don’t open in Application Guard windows even though they should.
- Fixed an issue where files that should be downloaded in Application Guard windows aren’t.
- Fixed an issue where an extra “Work” browser profile gets automatically created for some users (note that this may not remove the extra profile; a future fix will ensure that).
- Fixed an issue where the Mac Touch Bar sometimes doesn’t show the proper content.
- Fixed an issue where the Settings page constantly shows “looking for updates” without ever completing.
- Fixed an issue where certain settings are changeable even when they’re disabled.
- Fixed an issue where certain settings that are supposed to be enabled by default are disabled after performing a settings reset.
- Fixed an issue where the Delete button does not appear next to downloads that have been blocked by SmartScreen.
- Fixed an issue where the warning not to close the browser because a download is in progress appears even though the user isn’t downloading anything.
- Fixed an issue where websites that are blocked by SmartScreen aren’t removed from history.
- Improved scrolling behavior on the new tab page.
- Fixed some issues with the PDF toolbar’s hiding behavior.
- Fixed an issue where switching between IE mode tabs and non-IE mode tabs leaves webpages at the wrong zoom level on certain devices.
- Fixed an issue where no sites open in IE mode tabs when a certain combination of IE mode policies is applied.
- Fixed an issue where tooltips in Collections all say “collection content” instead of the actual content.
- Fixed an issue where certain print preview content is hard to read in dark theme.
We’ll be back to normal next week, and it’s also Ignite! Will we see any of you there? In the meantime though, thanks to everybody who’s been using Edge and telling us everything you do and don’t like about it.
134 Replies
josh_bodner
Hi Josh,
Reading view is, still, not showing all the photos/images in an article. It will show some from an article, maybe 1 or 2, but, not all that an article, actually, has. Reading view normally will show all the photos an article has.
The caret browsing is cool. Having Add notes will be, even, cooler. Just a matter of time, to be sure, since, I, already, know it is coming.
Cheers,
Drew- Yes add notes (or Web page inking) is now added in the list of the features being reviewed by the developers. more info:
https://techcommunity.microsoft.com/t5/Discussions/Top-feedback-summary-for-October-29/m-p/963887
josh_bodner Unfortunately, multiple desktop support has become worse since last week's dev update. When you open a link from another app inside a virtual desktop where there is no Edge window, instead of opening a new window what happens is that you are thrown into an existing window inside one of the other desktops. I find this a pretty strong regression and think it should be fixed for a beta build.
Apart from that, the only issue I have with Edge right now is how the taskbar icon and the start menu icon are strangely "disjoint" - i.e. they are not the same, so the one on the taskbar shows "pin to start" as an option and the one on start shows "pin to taskbar" as option, for some reason. This also means that their jumplists are out of sync. However, from what I can tell this is already an issue with the current beta.
Apart from that, I find the new Edge to be a fantastic experience and it's been my default browser since the first dev build. Keep up the great work!
adrianghc Totally agree on the virtual desktop behavior. That's driving me insane since it started happening!
seancorfield
No kidding, eh, Sean? And being so used to how things are supposed to work, keep going to do certain actions forgetting it's not working right or not going to ARrrrrrrr
"Oh, yes, can't/won't to that, grrrrr" SIGH! Ahem. Yes, it's aggravating. But, they do know about it & say they are working on a FIX. Like you, I hope it is soon. It used to be alright. We had this, briefly, in 10 before it was released; that was fixed quickly back then.
Cheers,
Drew
- Do you mean that the one on the taskbar is missing "unpin from taskbar" and the one on start menu is missing "unpin from start menu"?
if the answer is yes then it's a problem but if the answer is no then it's normal what you explained:
"the one on the taskbar shows "pin to start" as an option and the one on start shows "pin to taskbar" as option" adrianghc
Hi,
Ok, we have just updated Dev today and I can find no change to this issue (yet). I find it has been the same ever since it 'broke' recently & started no longer behaving properly, in this context. Certainly, I fully agree it ought be fixed before the next Beta. I will, tell you the developers ARE aware & say they are working on fixing it. Fingers crossed it's done by then.
As for what you have Start vs Taskbar, sounds strangely different than what I have or I'm misunderstanding what you have described. Below for your viewing & comments is from mine...
Cheers,
DrewDrew1903 Actually, your screenshots show part of what I mean. Observe how the jumplists are different on the start menu and on the taskbar. This is because they are not the same shortcut. Only the one in the taskbar shows the "right" jumplist. You can't get the same shortcut to behave correctly on both start menu and taskbar. If you pin the one from the taskbar to start, it shows a blank tile titled "W~MSEdgeDev.UserData.Default". If you pin the one from the start menu to the taskbar, then any windows you launch from it will spawn a new icon on the taskbar instead of being assigned to the icon you just launched from.
