Oct 29 2019 10:38 AM - last edited on Nov 04 2019 09:02 AM by Elliot Kirk
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.
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.
Oct 29 2019 11:48 AM - edited Oct 29 2019 11:50 AM
@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!
Oct 29 2019 11:51 AM - edited Oct 29 2019 12:30 PM
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.
Oct 29 2019 12:00 PM
Oct 29 2019 12:19 PM
Oct 29 2019 12:32 PM
Oct 29 2019 12:48 PM - edited Oct 29 2019 12:50 PM
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...
Oct 29 2019 12:54 PM
Oct 29 2019 01:16 PM
@Drew1903 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.
Oct 29 2019 02:51 PM
Just as a note for the next Edge Dev, Edge Canary has been seriously messed up and unusable for me since the first one after last weeks Edge Dev release. In Canary, every version since last Tuesday: (1) right clicking on a page - anywhere on a page - does not produce a context menu; (2) it causes lsass.exe to start running taking 11% cpu continuously; (3) closing it leaves two msedge.exe's still running in Task Manager and lsass.exe STILL taking 11% cpu, and Canary can't be restarted; (4) if I kill the leftover msedge.exes, then lsass.exe goes to normal 0% cpu and I can restart Canary, but with all the same problems every time. No Canary update since this started a week ago has changed anything. This latest Edge Dev does not show these problems, just Canary.
I reported it with Send Feedback, but just thought I'd mention it here.
Oct 29 2019 02:53 PM
Fair enough, Adrian. I believe, by design & intent, they are not the same. This you, eve, note & say yourself. But, each doing & offering what they do seems ok to me or IMHO. I don't see or find much different than the familiar or to what would be expected, traditionally. Admittedly, I may be the wrong person as I hardly ever turn to Start for anything... I'm more concerned with having everything copacetic at the taskbar & or elsewhere. I have preferred using the Applications window since sometime back in the early days of Win7.
Oct 29 2019 02:56 PM
@Drew1903 I disagree, I can't imagine this being intended and this behavior is inconsistent with every other program or app out there (Chrome Beta/Dev/Canary builds may have these problems as well, I don't know). Not to mention they used to be the same until about a month ago when this broke (just in time for the last beta release).