Jun 02 2020 10:56 AM
Jun 02 2020 10:56 AM
Hello Insiders! Today we’re releasing build 85.0.531.1 to the Dev channel. It’s a small week this week since it’s the first one for major version 85. Everything noteworthy it contains is:
As always, we couldn’t do this without you!
Jun 10 2020 10:58 AM
Jun 17 2020 05:21 PM
@Tom_Fox there is indeed: https://docs.microsoft.com/en-us/deployedge/microsoft-edge-policies#networkpredictionoptions. Since the implementation is something we've inherited from Google (minus any Google-specific services that we would have replaced with our own), there is lots of Google documentation you can refer to, for example: https://developers.google.com/web/updates/2018/07/nostate-prefetch. There are other things controlled by this setting/policy that I don't know of any documentation for though.
Jun 17 2020 05:25 PM
@Eyal_Shahar (and everybody else seeing favorites duplication) we've identified some new bugs in this area that we inherited from upstream Chromium. Both us on the Edge side and the folks working on Chromium are actively looking into it.
Jun 17 2020 05:31 PM
@Glowtape we've got some other reports of people on Windows 10 version 2004 experiencing bluescreens from their Nvidia 20x0 drivers while playing video in Edge. While we're looking into it, you might also try running Edge with the --disable-playready-hardware-drm flag, as that's helped some people, although doing so may limit the quality of video that you can view, so you'll want to remember to take that flag off once the issue gets fixed.
Jun 17 2020 05:36 PM
@waltnich in general, you can report issues by going to ... > Help and feedback > Send feedback. In this case, it would be helpful to know exactly what you're seeing when you say you can't log in. Is the page loading endlessly? Do you get an error from the website or from Edge? Is the page not loading at all? If it's that last one, we know we had an issue recently where clicking links from outside applications doesn't work if Edge has an update waiting to be installed (see our known issues).
Jun 18 2020 02:50 PM
Hello Josh. I get the problem randomly but always logging onto TD Bank. I will be using my experience with TD.
When I put in my credentials a pink box apears at the top of the credentials box that says "Something doesn't match. Please try again. You can also retrieve your user name or reset your password via the "Forgot user name and/or password?" link."
I contacted TD and they said they don't know what that is. They, from their end, tried to monitor my login but nothing is happening at their end. They offered that it is a browser issue. It started after the last build drop. @josh_bodner
Jun 19 2020 06:06 AM
No Josh. I do let the auto-fill option deploy and I have been using Last Pass forever - BUT, I have been manually inputting the TD Bank login.. I performed all of the steps you offered thru AI and your telephone tech who was certain he could fix it (but couldn't) He put in the ticket. I don't know if I am connected thru that contact or from requests I have made independently. But I've exhausted normal protocal@josh_bodner
Jun 23 2020 06:56 PM
@waltnich I promise I'm not It's just very hard to tell whether website issues are due to problems with the browser, the extensions you use, the website itself, user error, some configuration of the device you're using, etc. Asking about InPrivate, for example, was to try to rule out extension interference since extensions don't run in InPrivate by default. Another thing I'd be very interested in is if it works in Guest windows or new profiles. Figuring out exactly where a bug reproduces is almost as important as how to reproduce it, since that info (or trying a different browser altogether) would go a long way to ruling out if it's your specific Edge profile that's somehow gotten corrupted, which we've seen before.
Jun 25 2020 08:11 AM
Sorry Josh but it started to feel AI when you ask questions that were all done at the start. I think maybe somebody at MS hadtransferred me to a blog? or simular because they don't want to work on this. If so, just be honest with me. I don't accept the opportunity to use beta and then when it glitches you dump me. I thought the idea was that the glitch that hits me will hit others and MS wants to find these glitches. This is my only glitch but if you leave me with a one line "idea" every day, quite honestly, that's crap.@josh_bodner
Jun 25 2020 05:07 PM
@waltnich You're right, it's very possible this is something that might affect other people, which is why I'm trying to get as much information as possible about when you do and don't see it. I just don't know who you've already talked with to know what all they tried with you. I'd still like to know if it works in InPrivate in Edge, and if you're up for testing some more, if it works in a different profile (you can just create a new profile and then delete it when you're done). Also, when I said other browsers, I should have been more specific and said other versions of Edge. Since you're seeing this behavior in the Dev channel and it started recently, it would be good to download Canary and try it in there, which would be the best way to determine whether it's something wrong with the whole browser or just something that's gone wrong with your profile data, since those two possible bugs are in very different parts of the program.
Jun 26 2020 07:15 AM
Jun 28 2020 01:36 AM
@waltnich yeah, sorry, this probably isn't the best forum for actively getting you back into a working state; that's just not what our main focus is here, so it's good that you're also working with support agents. I don't know which support agents you've tried already, but in case you weren't aware, we've also got agents dedicated to the browser, and you can open a ticket from https://microsoftedgesupport.microsoft.com/hc/requests/new.