May 19 2020 10:48 AM
Hello Insiders! Today we’re releasing build 84.0.516.1 to the Dev channel. In community news, we’ve got another AMA coming up! It’s happening Thursday over on Reddit, see https://twitter.com/MSEdgeDev/status/1261029217132830720 for all the details. We’ve also got a discussion going around all the different ways you get back to websites you’ve been to before right here: https://techcommunity.microsoft.com/t5/discussions/discussion-getting-back-to-websites-important-to-.... Finally, we’ve got a preview of everything we’re going to talk about at Build 2020! Whether you’re a web developer, an IT manager, or a student, we’ve got something for you: https://blogs.windows.com/msedgedev/2020/05/19/microsoft-edge-news-developers-build-2020/. In product news:
Added features:
Improved reliability:
Changed behavior:
Known issues:
We hope you’ll tune into Build, and we’re also looking forward to hearing from you at our AMA. Everything we’re talking about has been shaped by you, and we’re looking forward to hearing how we can improve even more!
May 21 2020 01:13 AM
May 21 2020 02:14 AM
@Neon01 I think this feature would be a good candidate for having zone-level permissions. At present, the only options are
"Site permissions/ Serial ports
Will block if turned off"
May 21 2020 02:22 PM
@Klb123 If it works in Canary, that's a good sign that it might be something we just fixed. If it doesn't work in future Dev updates though, that probably means there's something with your profile's settings that's still causing problems. Can you get it to work in Dev if you use an InPrivate or Guest window?
May 21 2020 02:40 PM
May 22 2020 12:20 PM
@Klb123 In that case, let's just wait for a few days and see if the next Dev update helps.
May 23 2020 09:30 AM
May 25 2020 08:49 PM
@josh_bodner Noticed in this version of dev the old behavior where hitting ESC while in full-screen mode on MacOS takes the user out of full screen mode.
Ie, having a finder prompt (like uploading a file) or a web popup, want to cancel...hit esc...removed from full screen
This was changed/fixed in a version way way back, hope this isn't being pushed to the final build
May 25 2020 09:44 PM
@josh_bodner Thank you sharing Information.
It launches "In Private" mode with Classic Edge, IME changes "Private mode" too.
But, New Edge(Stable/Dev) launch "In Private mode", that IME can't changes to private mode.
IME suggestion is very sensitive privacy for almost APAC users. I expect Classic Edge and New Edge to work the same way.
May 26 2020 01:56 PM
@Kazushi KAMEGAWA Good news! We have a fix for this in the next version of Windows (you should be able to see for yourself if you're running Windows Insider builds right now). In that version, you should see the exact same behavior for TSF3 IME keyboards as you do in Edge Legacy.
May 26 2020 03:31 PM
@josh_bodner Thank you comment! I'm looking forward to next version. But Enterprise users still keep older version of Windows(1809, 1909). I hope to backporting this issue.
Jun 16 2020 10:20 AM - edited Jun 16 2020 10:31 AM
What's the "UI to help enable media casting if users attempt to use it while it’s disabled" supposed to look like? What is the expected experience here? I was trying to explain to another how to get Chromecast working in Edge, and was trying to explain forward to when Edge 84's mainstream, but even in Edge 85 I couldn't see anything materially different about the casting experience vs 83: the only device listed under "Cast media to device" is a Roku/non-Chromecast device. I didn't see a button or anything allowing me to opt-in to see the Cast protocol devices on the network. I suspect, as in Edge 83, I could enable flags to get Chromecasts to appear, but I think you're implying I shouldn't have to do that anymore in Edge 84+? What am I missing? Did this get backed out as of 84.0.522.20?
Jun 17 2020 04:47 PM
@Wade Dorrell you're looking for this:
It appears when you try to cast something but casting is completely disabled for the browser. When you click Restart, the appropriate flags are set automatically for you, as opposed to having to enabled them manually like before. This has nothing to do with which devices are eligible to cast to though; if we didn't support it before this change, that won't be any different now. We're still looking into how we can improve the types of devices we can to in the future.