Microsoft releases a new update for Edge 131 and it brings major changes to the browser's policies

The patch is now available to download.

Reading time icon 2 min. read


Readers help support Windows Report. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help Windows Report sustain the editorial team. Read more

Microsoft Edge 131

Microsoft has released a significant update for its browser, Edge, in the Stable Channel with Version 131. It is now available to all users with many improvements, updates, policy changes, security fixes, and more.

Microsoft Edge changed the behavior of the cancel dialog for the beforeunload event. Calling event.preventDefault in a beforeunload event handler won’t prevent the dialog from being shown. Instead, event.returnValue = ” it needs to be called in the beforeunload event handler to prevent the cancel dialog. The BeforeunloadEventCancelByPreventDefaultEnabled policy is obsolete and no longer works after Microsoft Edge version 130.

The Kyber algorithm was standardized with minor technical changes and renamed to the Module Lattice Key Encapsulation Mechanism (ML-KEM). ML-KEM is implemented in the BoringSSL cryptography library, allowing it to be deployed and utilized by services that depend on this library. The changes to the final version of ML-KEM make it incompatible with the previously deployed version of Kyber. Due to this incompatibility, the following changes in Microsoft Edge will be made:

  • Edge switches from supporting Kyber to ML-KEM.
  • Edge offers a key share prediction for hybrid ML-KEM (codepoint 0x11EC).
  • The PostQuantumKeyAgreementEnabled flag and the PostQuantumKeyAgreementEnabled policy applies to Kyber and ML-KEM. Note: The PostQuantumKeyAgreementEnabled policy is scheduled for removal in Edge version 141.
  • Edge will no longer support hybrid Kyber (codepoint 0x6399).

The EdgeSidebarAppUrlHostAllowList policy allows admins to define a list of sites, based on URL patterns, that are not subject to the EdgeSidebarAppUrlHostBlockList. When the policy is configured, the apps listed in the allow list can be opened in the sidebar even if they are listed in the block list. For more information, see Manage the sidebar in Microsoft Edge.

You can read the whole changelog to Microsoft Edge 131 here.

In other news, the Redmond-based tech giant is adding a new feature usage capability to Microsoft Edge, allowing users to aggregate data on their Edge usage across all platforms in one single place.

More about the topics: Edge, microsoft

User forum

0 messages