Microsoft has launched a significant replace for its browser within the Stable Channel. Version 131 is now to be had to all customers, providing many small enhancements, some characteristic updates, coverage adjustments, safety fixes, and extra.
Here is the changelog with characteristic updates in Microsoft Edge 131:
Cancel conversation for beforeunload match. Microsoft Edge modified the habits of the cancel conversation for the beforeunload match. Calling match.preventDefault in a beforeunload match handler would possibly not save you the conversation from being proven. Instead, match.returnValue=”” must be referred to as within the beforeunload match handler to stop the cancel conversation. The BeforeunloadEventCancelByPreventDefaultEnabled coverage is out of date and now not works after Microsoft Edge model 130.
Changes to Kyber. The Kyber set of rules was once standardized with minor technical adjustments and renamed to the Module Lattice Key Encapsulation Mechanism (ML-KEM). ML-KEM is carried out within the BoringSSL cryptography library, which permits for it to be deployed and used by products and services that rely on this library.
The adjustments to the overall model of ML-KEM make it incompatible with the in the past deployed model of Kyber. Due to this incompatibility the next adjustments in Microsoft Edge might be made:
- Edge switches from supporting Kyber to ML-KEM.
- Edge provides a key percentage prediction for hybrid ML-KEM (codepoint 0x11EC).
- The PostQuantumKeyAgreementEnabled flag and the PostQuantumKeyAgreementEnabled coverage applies to Kyber and ML-KEM. Note: The PostQuantumKeyAgreementEnabled coverage is scheduled for elimination in Edge model 141.
- Edge will now not enhance hybrid Kyber (codepoint 0x6399).
New sidebar coverage. The EdgeSidebarAppUrlHostAllowList coverage lets in admins to outline a listing of websites, in accordance with URL patterns, that don’t seem to be topic to the EdgeSidebarAppUrlHostBlockList. When the coverage is configured, the apps indexed within the permit listing may also be opened in sidebar despite the fact that they’re indexed within the block listing. For additional information, see Manage the sidebar in Microsoft Edge.
Microsoft Edge 131 additionally comprises the entire fixes and small enhancements from the former 4 Edge 131 Dev updates. You can test the ones unencumber notes intimately right here:
-
Dev Channel replace to 131.0.2863.0
-
Dev Channel replace to 131.0.2875.0
-
Dev Channel replace to 131.0.2889.0
-
Dev Channel replace to 131.0.2903.5
Finally, Edge 131 patches a number of safety vulnerabilities. One is Edge-specific (CVE-2024-49025), and 8 are Chromium-related. More information about the safety fixes are to be had within the Security Update Guide.
No Comment! Be the first one.