Forum Discussion
josh_bodner
Microsoft
MicrosoftDev channel update to 90.0.803.0 is live
Hello Insiders! Today we’re releasing build 90.0.803.0 to the Dev channel. We’ve got some cool things to talk about up front, and here they are:
- First, if you’ve ever wondered what a cookie really is while you’re surfing, we’ve got a great introductory article that explains everything you need to know: https://www.microsoft.com/en-us/windows/remote-resource-center/manage-web-cookies.
- Next, for web devs, we’ve got not one, but two exciting articles! Here, we’ve got some hints and tips to help you save time and work smarter when using the F12 tools: https://blogs.windows.com/msedgedev/2021/02/23/six-time-saving-tips-edge-devtools-console/.
- And here, for PWA devs, we’ve got an overview of some of our recent work to improve service worker debuggability: https://blogs.windows.com/msedgedev/2021/02/22/service-worker-tools-network-application-sources/.
- Finally, for enterprise and IT folks, we’re excited to announce a change to our auto sign-in behavior for on-premises accounts: https://techcommunity.microsoft.com/t5/enterprise/updates-to-auto-sign-in-with-on-prem-active-directory-accounts/m-p/1185301.
As for everything that’s new feature-wise:
Added features:
- Added the ability to customize keyboard shortcuts in the F12 Dev Tools.
- Added support for showing the friendly name of a certificate when viewing its details in the Windows certificate viewer.
- Enabled the redesigned, smaller context menus for PDFs by default.
- Enabled support for the management policy to control Print Rasterization Mode from Chromium.
Improved reliability:
- Fixed a crash on launch.
- Fixed a crash when closing a tab.
- Fixed a crash when Sharing something.
- Fixed a crash when typing into the address bar.
- Fixed a crash when using speech recognition on Google websites.
- Fixed an issue where using the Web Widget in Guest windows sometimes crashes the browser.
- Fixed an issue where tabs sometimes are blank or frozen after being left alone for a while.
- Fixed an issue where printing sometimes fails with a message that it “can’t calculate”.
Changed behavior:
- Fixed an issue where filtering cookies on edge://settings/siteData fails.
- Fixed an issue where Edge tabs sometimes don’t appear in the Windows Alt+Tab list when expected.
- Fixed an issue where attempting to Modify Edge’s installation from Windows’ list of installed programs does nothing.
- Fixed an issue where opening Edge via a Taskbar shortcut sometimes results in a window that isn’t associated with that shortcut.
- Fixed an issue where searching to type in the History or Favorites flyout sometimes stops working while typing.
- Fixed an issue where opening an Edge window by clicking on a website’s notification results in the window not being associated with existing Taskbar shortcuts.
- Fixed an issue where newly-installed PWA or websites sometimes get pinned to the Start menu or Taskbar unexpectedly.
- Fixed an issue where Single Sign-On doesn’t work for some work/school users.
- Fixed an issue where pasting into a text note in Collections sometimes fails.
- Fixed an issue where dropdowns on webpages sometimes prevent users from interacting with other items on the page.
- Fixed an issue where interactions with the Password Monitor popup don’t work.
- Fixed an issue where the wrong context menu sometimes appears in the Collections flyout.
- Fixed an issue where entering fullscreen turns off vertical tabs after exiting fullscreen.
- Fixed an issue where search suggestions sometimes don’t appear in the Web Widget.
- Fixed an issue where the Web Widget sometimes goes blank or black, but links can still be clicked.
- Fixed an issue where Password Monitor scans never appear to finish.
- Fixed an issue where the management policy to configure Restore On Start Up URLs sometimes doesn’t work properly when configured as “recommended”.
- Removed the ability to pin a website to the Taskbar from the edge://apps context menu.
Known issues:
- Certain extensions such as the Microsoft Editor extension don’t work on Linux. As soon as they’re installed, they crash and are disabled. We’re currently investigating.
- Users of certain ad blocking extensions may experience playback errors on Youtube. As a workaround, temporarily disabling the extension should allow playback to proceed. See https://techcommunity.microsoft.com/t5/articles/known-issue-adblock-causing-errors-on-youtube/m-p/14... for more details.
- Some users are still running into an issue where all tabs and extensions immediately crash with a STATUS_INVALID_IMAGE_HASH error. The most common cause of this error is outdated security or antivirus software from vendors like Symantec, and in those cases, updating that software will fix it.
- Users of the Kaspersky Internet Suite who have the associated extension installed may sometimes see webpages like Gmail fail to load. This failure is due to the main Kaspersky software being out of date, and is thus fixed by making sure the latest version is installed.
- Some users are seeing favorites get duplicated after we made some previous fixes in that area. The most common way this is triggered is by installing the Stable channel of Edge and then signing into it with an account that has already signed into Edge before. This issue should be reduced now that automatic deduplication has been introduced into Insider channels. However, we’ve also seen duplication happen when running the manual deduplicator on multiple machines before either machine has a chance to fully sync its changes, so while we wait for the automatic deduplication to make it to Stable, make sure to leave plenty of time in between runs of the deduplicator.
- Some users are seeing “wobbling” behavior when scrolling using trackpad gestures or touchscreens, where scrolling in one dimension also causes the page to subtly scroll back and forth in the other. Note that this only affects certain websites and seems to be worse on certain devices. This is most likely related to our ongoing work to bring scrolling back to parity with Edge Legacy’s behavior, so if this behavior is undesirable, you can temporarily turn it off by disabling the edge://flags/#edge-experimental-scrolling flag.
As always, we couldn’t do all this without your valuable input!
- Spoiler
SLDimuthu1 wrote:josh_bodner MS build , build in Antivirus engine to edge like chrome
what chrome has is bloatware, they put a 3rd party tool in their browser that nobody asked for.
and that tool gathers and sends user data to a 3rd party company and their server.
Edge already uses Windows Security's (Defender) features to protect users.
edge://settings/privacy
- I say like in mac os
I would like to thank you for articles, several people asked me why one specific anti-malware detects Cookie but Windows Defender won't and they complain like Microsoft Edge is NOT protecting their privacy and I need to share same story of cookies over and over. But the article is very helpful.
Good to see new features and bug fixes and hope known issue will be fixed soon.
- Trying once again - I still have the issue that a new browser windows always opens with an additional "default" tab, although it is set to open recently open tabs. Browser window shows as the following when opened:
<new tab page> | <previously opened tab 1 > | <previously opened tab X...>
Anyone else has this problem?- josh_bodner
cloud_entropy As I recall, nobody internally could reproduce the extra new tab on startup issue, so I'm curious if you can reproduce it in a different profile in the same Edge channel, and also in a new Edge channel like Canary (if you're currently using Dev). If you can, that would seem to point to something on your device that's causing this like HotCakeX mentions. Is this device a personal one or one you use at work?
- Spoiler
cloud_entropy wrote:
Trying once again - I still have the issue that a new browser windows always opens with an additional "default" tab, although it is set to open recently open tabs. Browser window shows as the following when opened:
<new tab page> | <previously opened tab 1 > | <previously opened tab X...>
Anyone else has this problem?I'm trying right now, on a fresh Windows 10 installation that i did the other day (latest version) on Edge Version 88.0.705.74 (Official build) (64-bit) (which is also the latest)
in edge://settings/onStartup set it to "Continue where you left off"
and i can not reproduce this issue. I open 3 tabs, close Edge and reopen it, i still have 3 tabs, nothing extra.
I think there is something else causing that problem in your environment. maybe a user configuration somewhere else, maybe a group policy.
what I can say with 100% certainty is that this doesn't happen on a new installation on OS/browser.
- Hey, the cookies flyout text in Brazilian Portuguese was partially fixed. It only shows the right text when Edge blocks only one third-party cookie in the page. If it's more than one, the old text is shown.
- josh_bodner
Hey, the cookies flyout text in Brazilian Portuguese was partially fixed. It only shows the right text when Edge blocks only one third-party cookie in the page. If it's more than one, the old text is shown.
eduardobragaxz I think we'll need to count this as a separate bug, so if you wouldn't mind filing feedback for this, that'll create a new bug in our system.
josh_bodner ok HotCakeX here is an illustration of how "just sticking an arrow in the upper right" doesn't work. Also whenever you click on the any content in the content window unless you have the content pinned, it disappears and the download content is hidden, the same happens if you resize the window in any way. This does NOT happen with the download bar at the bottom. Even if it can only show ONE file it at least shows that one, always in the same place relative to content.
josh_bodner here is an example of why moving the download bar from the bottom is a bad idea. There are literally thousands of sites with designs like this - all trying to help people find their downloads and use them properly. Your redesign SCREWS THESE UP - and confuses users when they don't see what the site is telling them to look for. Please restore the bottom bar. If you want a drop down download manager make it OPTIONAL or allow BOTH. But don't make it the default.
- Spoiler
Lee Drake wrote:josh_bodner here is an example of why moving the download bar from the bottom is a bad idea. There are literally thousands of sites with designs like this - all trying to help people find their downloads and use them properly. Your redesign SCREWS THESE UP - and confuses users when they don't see what the site is telling them to look for. Please restore the bottom bar. If you want a drop down download manager make it OPTIONAL or allow BOTH. But don't make it the default.
just draw the same arrow in the opposite way, pointing to the top right instead of bottom left, problem fixed.
it's not really necessary to draw and arrow for people, nowadays websites rarely do this. but if that's what you wanna do, draw an arrow pointing to the top right.
Edge is not the only browser with a Modern flyout experience, Firefox which is the 3rd popular browser does the same. I don't even remember Opera, Vivaldi, Yandex, Safari etc.
the thing is, when a download is offered, Edge makes it very clear to the user and asks for input.
Lee Drake one of the best things about the download bar is that NEW DOWNLOADS appear in a predictable place where the browser could literally point to it and it was ALWAYS THERE. The new "download manager" doesn't offer that option. Depending on scroll position the download may be off the screen above the top scroll. The manager will drop down "wherever" relative to the content on the screen. Walking a user through using a downloaded file is now much more difficult if they're not used to looking for it in the manager, and depending on settings may be hidden altogether. It may be fine for experts, but for neophyte users it's going to be MORE confusing - especially if switching from another browser.
- Spoiler
Lee Drake wrote:Lee Drake one of the best things about the download bar is that NEW DOWNLOADS appear in a predictable place where the browser could literally point to it and it was ALWAYS THERE. The new "download manager" doesn't offer that option. Depending on scroll position the download may be off the screen above the top scroll. The manager will drop down "wherever" relative to the content on the screen. Walking a user through using a downloaded file is now much more difficult if they're not used to looking for it in the manager, and depending on settings may be hidden altogether. It may be fine for experts, but for neophyte users it's going to be MORE confusing - especially if switching from another browser.
Are you sure you're looking at the right thing?
the new downloads flyout experience never does that. the downloads prompt always shows up in a Fixed place, top-right side of the browser, the designated area for Edge toolbar items.
not just anywhere on the screen and definitely not depended on the scroll position.
I've been trying the new flyout download experience ever since it was added to Edge canary, it never appeared anywhere else other than its designated place.
When I try to "Send Feedback" (or press Alt-Shift-I) it hangs Edge. I tried it couple times with same result.
- josh_bodner
When I try to "Send Feedback" (or press Alt-Shift-I) it hangs Edge. I tried it couple times with same result.
mkoninin If you create a new profile, does the same thing happen there? If so, would it be possible to install a different Edge channel and send feedback from there that sending feedback froze in a different channel? It will at least get some machine-level logs that could be useful, and will more importantly create a bug in our system.
- Spoiler
mkoninin wrote:When I try to "Send Feedback" (or press Alt-Shift-I) it hangs Edge. I tried it couple times with same result.
when that happens, press Ctrl + Alt + Delete,
then select task manager, once task manager opens, close it. this should help getting unstuck and continue sending your feedback.
happened to me once or twice and i used that method.
josh_bodner new build, same problem...
When starting the browser, the window stays empty for some seconds. I also get this error message:
"Profile error. Some features may not be available. An error has occurred."
If I confirm this with ok, everything actually works. I've signed out and signed in again, deleted all data, but the problem persists.
- josh_bodner
When starting the browser, the window stays empty for some seconds. I also get this error message:"Profile error. Some features may not be available. An error has occurred."
bigfraggle007 as others have seen, this is fixed in current Canary builds and so it should be fixed in next week's Dev.
bigfraggle007 same issue!
- Spoiler
@josh_bodner new build, same problem...
When starting the browser, the window stays empty for some seconds. I also get this error message:
"Profile error. Some features may not be available. An error has occurred."
If I confirm this with ok, everything actually works. I've signed out and signed in again, deleted all data, but the problem persists.
Update: I've cleared again all data and cache and now Edge starts immediately without a error message.
But suddenly I'm getting this profile error message when closing the browser.
bigfraggle007 I am also seeing this new error in the new browser.
- This little thing gives me headache 😞 honestly...
- josh_bodner
yoSachin I think I replied on one of the older release notes, but what's going on here is that a fix we made for some devices' scrolling behavior has unfortunately regressed the behavior on other devices. Because of the wide range of device types and drivers out there, there's not really anything we can do to fix everything with just one set of code, so we're instead going to work on a way to choose between the new version or the old version (that worked for you) via a flag, but that will take some time.
Hello josh_bodner
I have a big issue with the last update on dev channel.
All context menu labels inside developers tools disappears !
Any ideas ?
This has already been fixed in Canary 90.0.804.0. I even assumed that the next dev version would be exactly 804, but for some reason they chose the broken 803
