Policy updates to allow wildcards.

Version 129.0.2792.52: September 19, 2024
Fixed various bugs and performance issues, feature updates, site impacting compatibility changes, and policy updates.

Stable channel security updates are listed here.

Fixes
Policy updates to allow wildcards. The documentation for the following policies were inaccurate and were corrected. These policies support wildcards (*) in URL patterns when being configured: ImagesAllowedForUrls, ImagesBlockedForUrls, InsecureContentAllowedForUrls, InsecureContentBlockedForUrls, PopupsAllowedForUrls, PopupsBlockedForUrls.

Feature updates
Update to Microsoft Edge supported operating systems. The minimum supported macOS version is increased to macOS 11. Users on older versions of macOS will no longer receive Microsoft Edge updates. For more information, see Microsoft Edge Supported Operating Systems.

Deprecation of the CryptoWallet feature. To improve end user experience, the CryptoWallet feature and the CryptoWalletEnabled policy is deprecated. The CryptoWalletEnabled policy will be obsolete in an upcoming release.

Site compatibilty impacting changes

• Deprecation of non-standard declarative shadow DOM serialization. The prototype implementation, which shipped in 2020 and then updated in 2023, contained a method called getInnerHTML() that could be used to serialize DOM trees containing shadow roots. That part of the prototype was not standardized with the rest of the declarative shadow DOM, and has only recently reached spec consensus (for details, see Github. As part of that consensus, the shape of the getInnerHTML API changed.
• Deprecate the includeShadowRoots argument on DOMParser. The includeShadowRoots argument was a never-standardized argument to the DOMParser.parseFromString() function, which was there to allow imperative parsing of HTML content that contains declarative shadow DOM. This was shipped as part of the initial shipment of declarative shadow DOM. Since the standards discussion rematerialized in 2023, the shape of DSD APIs changed, including this feature for imperative parsing.

Now that a standardized version of this API, in the form of setHTMLUnsafe() and parseHTMLUnsafe() shipped, the non-standard includeShadowRoots argument needs to be deprecated and removed. All usage should shift accordingly:
Instead of:
(new DOMParser()).parseFromString(html,'text/html',{includeShadowRoots: true});
This can be used instead:

document.parseHTMLUnsafe(html);

Rename inset-area to position-area. The CSS working group (CSSWG) resolved to rename this property from inset-area to position-area. For more details, see the CSSWG discussion in Github.

The old and new property names will be supported for a few milestones, to help developers migrate to the new position-area name. We are shipping the new property name, position-area, as a synonym for inset-area.

The inset-area property is currently planned for removal in Microsoft Edge version 131.