Microsoft has updated the Microsoft Edge Addons Store with review & Rating system support for Extensions and Editors' Picks
In light of the current circumstances, the Edge team will pause updating the Stable channel to Edge 81 consistent with the Chromium Project. We are committed to continued security and stability updates to Edge 80. We’ll have more to share on this next week.
|Microsoft Edge Version||Date Released||Based on Chromium Version||Chrome Release Blog||Highest Severity Fix in Release||CVEs|
|80.0.361.69||3/19/2020||80.0.3987.149||Chrome Releases Blog||High||CVE-2020-6422, CVE-2020-6424,CVE-2020-6426,CVE-2020-6427,CVE-2020-6428, CVE-2020-6429,CVE-2019-20503,CVE-2020-6449|
Updated 3/31/2020 – Following the updated Chromium schedule, we are adjusting our schedule for upcoming Microsoft Edge releases and cancelling the version 82 release. Microsoft Edge 81 will release to Stable in early April, followed by an early release of Microsoft Edge 83 in mid-May.
As announced in October of 2018, Microsoft will soon disable Transport Layer Security (TLS) 1.0 and 1.1 by default in Microsoft browsers. In light of current global circumstances, we will be postponing this planned change—originally scheduled for the first half of 2020.
For the new Microsoft Edge (based on Chromium), TLS 1.0 and 1.1 are currently planned to be disabled by default no sooner than Microsoft Edge version 84 (currently planned for July 2020).
For all supported versions of Internet Explorer 11 and Microsoft Edge Legacy (EdgeHTML-based), TLS 1.0 and TLS 1.1 will be disabled by default as of September 8, 2020.
While these protocols will remain available for customers to re-enable as needed, we recommend that all organizations move off of TLS 1.0 and TLS 1.1 as soon as is practical. Newer versions of the TLS protocol enable more modern cryptography and are broadly supported across modern browsers, such as the new Microsoft Edge.
Changelog is up:Edge just got an update to version 80.0.361.109.
No changelog yet here:
Releases blog link had an extra "l" at the end of it Chrome Releases
Can you give a link to the feature requests?FYI
I had requested (like more Members on this forum) for some changes in the new tab page
Search engine box on new tab page.
Currently only Microsoft's own Bing Search engine is displayed at the center of the New Tab Page (even when you change the search engine for the adres bar). It seems from they will implement this request in an upcoming release. Because Microsoft did not exactly mention how they will implement this, I guess they will use the same search engine as the user specified as search engine (for the adress bar).
Blank new tab page
Old Edge had the option to display a completely blank new tab page. This will be implemented in new Edge chromium in future.
At the same time (october 2019) I had also requested for a more privacy respecting smartscreen URL check mechanism. Have not heard about that request (and it is also not listed in the feature request list, so I think that one is rejected).
They claim they've implemented the ability to hide the search bar in the dev/canary builds but I don't see the option in either build. So either they haven't or it's incredibly well hidden.They are right at the top currently: Top Feedback Summary for March 31
I got two emails for first and second (the third-one is already implemented for active directory and device managed instances, see link NewTabPageLocation). Although they have no ETA yet, it seems they have decided to assign resources to those requests.
View attachment 236283
View attachment 236285
View attachment 236286