Aug 05 2020 10:56 AM
Hello Insiders! Today we’re releasing build 86.0.594.2 to the Dev channel. Outside of the Dev channel, we’re excited to announce that Collections are now available for mobile users! See https://blogs.windows.com/msedgedev/2020/07/29/collections-is-now-available-on-the-microsoft-edge-mo... for what to expect. As for everything that’s new and noteworthy in the product:
Added features:
Improved reliability:
Changed behavior:
Known issues:
As always, we couldn’t do this without you, and a special thanks to our Collections users for their help in getting the feature onto mobile!
Aug 05 2020 11:31 AM
@josh_bodner I now see the Alt-Tab settings options to display none, some, all Edge tabs when pressing alt-tab but no matter which option I choose, I only see open windows and not all the open tabs.
Aug 05 2020 12:12 PM
Aug 05 2020 12:58 PM
Nice to see the Tab Hover Card Images flag turn up that's been in Google Chrome for ages.
And it would have been nice that we finally got access to the edge:flags page in the last Android Edge release ... apart from the fact that it only shows ONE flag!
But ...
Still no History and Open Tabs sync in desktop or Android Edge. In a world where most people have a smart phone, and a lot of them also a desktop/laptop so likely to need syncing, it beggars belief you'd public release the software without all the syncs, and even more we'd be this many months along still without it.
The no-rubber-banding scrolling personality switch is still a flag, not a setting, and you are STILL saying in each of these Dev release posts that the ability to turn it off and keep normal scrolling is temporary. So long as that is the case I will never change to Edge.
And still no ability to pin chosen topsites to the new tab page or have 'darkified' web pages in Android Edge.
So I run each release of desktop Canary and Dev and Android Beta precisely once for about two minutes just to check for any development in any of these things, and week after week, month after month there's none, while the developers play around with adding more and more pretty bells and whistles I couldn't care less about.
The fact that there have been so many desktop and Android releases over so many months without a single one of the issues I care about progressed at all leaves me very depressed and ready to give up. And now your colleagues have screwed up the Microsoft Launcher for Android, while other of your colleagues have screwed up To Do. I'm thinking its time to give up on Microsoft software.
Aug 05 2020 04:04 PM
Not sure if this has been addressed but while using build 86.0.587.0 on Windows 10 version 2004, there seems be an issue with uploading pictures to Facebook. When I try upload pictures to Facebook, the dialog box appears behind the Edge window and full screen. This also freezes my computer for a few seconds. I have only noticed this strange behavior when I use Facebook. I often upload pictures to Weebly without any issue.
Aug 05 2020 06:41 PM
@david-bell the Edge feature responsible for telling windows about all its open tabs so it can put them in the alt+tab menu had to be temporarily disabled (it was one of the causes of the fullscreen issues people have been seeing recently), so that's probably why it's not working at the moment.
Aug 05 2020 06:41 PM
@tobassam900 We've got an engineer working on it! A lot more people started reporting it over the past week for some reason, which helped bring it to our attention.
Aug 05 2020 06:42 PM
@js123 when you say "behind", is it still usable, but just has to be brought to the foreground, or is it functionally broken when that happens?
Aug 05 2020 06:47 PM
It is functionally broken when that happens. I can't use Alt-Tab or Windows-Tab to bring it forward.
Aug 06 2020 03:12 AM
@josh_bodner Hi! Just updated to this version and the "Display variable values inline while debugging" in DevTools is no longer working.
I've tried deselecting the setting and selecting it again, computer restart and no luck.
Is there anything I can provide you with ofr further analysis of the issue?
Thanks!
Aug 06 2020 08:40 AM
I still get a crash every time Edge updates if I click on the update window "Close" button after the browser has relaunched with the new version. The only way to not get the crash is to quit the browser, then click "Close" and relaunch the browser once again.
Aug 06 2020 02:47 PM
@js123 do you know if it's only happening in your profile? Like, does it happen in Guest windows? Or can you install Canary and see if it happens there too?
Aug 06 2020 02:50 PM
@divosuplente can you file feedback from within the F12 tools? That will both get the relevant logs as well as make sure it opens a bug in our database.
Aug 06 2020 02:59 PM
@dejan008 is the crash any time you close the window after updating, or is it just if you close it very soon after the update happens?
Aug 06 2020 05:45 PM - edited Aug 07 2020 01:39 AM
Update: For anyone interested, it's a bug in the chromium core, related to a change in the SVG engine. They meanwhile fixed it in Chrome Canary v 86.0.4226.0, so hopefully it will be included in Edge Dev and Canary within the next couple days.
https://bugs.chromium.org/p/chromium/issues/detail?id=1108966&q=discord&can=2
Since v 86.0.594.1 I can't login to discord anymore, on both Dev and Canary. I've tested on different machines, I always just get this error screen:
And yes, it definitely worked before the update to 86.0.594.1.
Please help!
Aug 06 2020 06:29 PM
@josh_bodner I do let the browser fully load (several windows open and probably 30-40 tabs total). Then I did wait another 10 seconds or so and only then pressed the "Close" button the last time. One of the previous upgrades when the crash happened I did send feedback using the Edge "Send Feedback" feature so you should have the relevant logs from that one.
Aug 06 2020 09:30 PM
Aug 06 2020 10:56 PM
@josh_bodner Hi! Never done it, but will try :) FYI, I've tried it in InPrivate mode, and the same is happening. Also, it doesn't happen in Canary.
Thanks!
Aug 07 2020 06:36 PM
@Neon01 We've pumped in the fix, but it's still in the process of being merged. So unfortunately since it didn't make it into today's Canary, it likely also won't be in Dev until the week after next.
Aug 07 2020 06:42 PM
@dejan008 Good to know, our system does look for crashes that happen around the same time as when feedback is sent, so we've definitely got it then. One other thing to look out for if you've got Canary installed is if the same thing happens there. If not, we've either already fixed it, or it's something about your specific Dev install or profile that's leading to it.