Edit

Share via

Release notes for Microsoft Edge Stable Channel

  • Article

These release notes provide information about new features and non-security updates that are included in the Microsoft Edge Stable Channel.

To understand Microsoft Edge channels, see the Overview of the Microsoft Edge channels.

Note

For the Stable Channel, updates will roll out progressively over one or more days. To learn more, see Progressive rollouts for Microsoft Edge updates.

Microsoft Edge Web Platform constantly evolves to improve user experience, security, and privacy. To learn more, see Site compatibility-impacting changes coming to Microsoft Edge.

Version 130.0.2849.68: October 31, 2024

Fixed various bugs and performance issues, improved reliabilty.

Stable channel security updates are listed here.

Improved reliability

  • Fixed a renderer crash (STATUS_BREAKPOINT) that occurred when using some sites with web contents accessibility enabled.

Version 130.0.2849.56: October 24, 2024

Fixed various bugs and performance issues.

Stable channel security updates are listed here.

Fixes

  • Fixed an issue which prevented some browser extensions using the chrome.storage.managed API from functioning correctly.

Version 130.0.2849.52: October 22, 2024

Fixed various bugs and performance issues, improved reliability.

Improved reliability

  • Fixed a browser crash that occurred on startup in On-premises environments when creating a new Microsoft Edge profile.

Version 130.0.2849.46: October 17, 2024

Fixed various bugs and performance issues, Dev channel updates, announcements, feature updates, site compatibility impacting changes, and policy updates.

Note

Portions of this release note are modifications based on work created and shared by Chromium.org and used according to terms described in the Creative Commons Attribution 4.0 International License.

Stable channel security updates are listed here.

Dev Channel updates

The following Dev channel updates preceded this Stable channel release. The following Dev notes provide detailed information about the changes in each release.

Fixes

  • Fixed an issue that prevented the briefcase icon from appearing on the edge://settings/sidebar page when Edge Bar was disabled using the StandaloneHubsSidebarEnabled policy.

  • Fixed an issue that caused rendering issues on some SharePoint sites.

  • Fixed an issue where a "Can't update Microsoft Edge" dialog was mistakenly shown for managed Windows devices.

Announcements

  • Live Captions. The LiveCaptionsAllowed policy was available since Microsoft Edge version 103 but this feature isn't generally available. Clients that have the ExperimentationAndConfigurationServiceControl policy set to 'FullMode' might receive the feature before broad availability. Broad availability will be announced via Microsoft Edge release notes.

  • Cancel dialog for beforeunload event. Microsoft Edge is changing the behavior of the cancel dialog for the beforeunload event in Microsoft Edge version 131. Starting in version 131, calling event.preventDefault in a beforeunload event handler won't prevent the dialog from being shown. Instead, event.returnValue = '' needs to be called in the beforeunload event handler to prevent the cancel dialog. The BeforeunloadEventCancelByPreventDefaultEnabled policy is being obsoleted and will no longer work after Microsoft Edge version 130.

Feature updates

  • Token Binding. Token Binding uses cryptographic certificates on both ends of the TLS connection in an attempt to close the security gap of bearer tokens, which may be lost or stolen. Token Binding is deprecated in Microsoft Edge version 130. Also, the AllowTokenBindingForUrls policy is now obsolete.

  • Copilot browser Context Policies. The EdgeEntraCopilotPageContext policy will be available starting from Microsoft Edge version 130 and will replace the CopilotCDPPageContext policy. The CopilotCDPPageContext policy is deprecated in Microsoft Edge version 130 and will be obsolete in Edge 133.

  • Elevating top settings and improving settings page navigability. To make finding browser settings more efficient, Microsoft Edge is introducing three navigation improvements to Edge Settings. We aren’t changing the functionality of any setting, and all the settings stay on the same page as they are today but will be behind clickable sections. These changes are as follows.

    • Introduce quick access to the most used Settings actions on the first place users land when entering Edge Settings (the Profiles page). Clicking the button with the name of the setting navigates users directly to its location.

    • Make densely populated Settings pages (such as Privacy, search, and services, Appearance, Cookies and site permissions, System and performance) easier to navigate by introducing quick access to the most used actions located on that page. Clicking the button with the name of the setting takes users directly to its location.

    • For these densely populated pages, each lengthy section of settings will be a clickable "table of contents" with descriptive subtexts. This helps users locate settings directly and avoid unnecessary scrolling.

    Note: This feature is a controlled feature rollout. If you don't see this feature, check back as we continue our rollout.

  • Edge on macOS now seamlessly opens links in Teams. When Microsoft Edge is configured as the browser to open web links in Teams, then links in Teams chat will be opened through Edge, and Edge launches in the profile that matches with the authenticated profile, users can benefit from a seamless browsing experience that integrates their identity and user data across Microsoft apps. Administrators can control the availability of this feature using the "Choose Which Browser Opens Web Links" Microsoft 365 policy. Note: This feature is a controlled feature rollout. If you don't see this feature, check back as we continue our rollout.

Site compatibility impacting changes

  • Compression dictionary transport with shared Brotli and shared Zstandard. This feature adds support for using designated previous responses, as an external dictionary for content encoding compressing responses with Brotli or Zstandard.

    Enterprises might experience potential compatibility issues with enterprise network infrastructure that intercepts HTTPS traffic and is sensitive to unknown content encodings. The CompressionDictionaryTransportEnabled policy is available to turn off the compression dictionary transport feature.

  • Keyboard focusable scroll containers. This feature improves accessibility by making scroll containers focusable using sequential focus navigation. Today, the tab key doesn't focus scrollers unless tabIndex is explicitly set to 0 or more.

    By making scrollers focusable by default, users without a mouse can now focus clipped content using tab and arrow keys. This behavior is enabled only if the scroller does not contain any keyboard-focusable children. This logic is necessary so there are no regressions for existing focusable elements that might exist within a scroller like a <textarea>.

    If more time is needed to adjust to this new feature, the KeyboardFocusableScrollersEnabled policy is available from Edge 128.

  • Support non-special scheme URLs. Non-special scheme URLs are now supported, for example, git://example.com/path. Previously, the URL parser didn't support non-special URLs. The parser parses non-special URLs as if they had an opaque path, which is not aligned with the URL standard. Now, the URL parser parses non-special URLs correctly, following the URL standard. For more details, see http://bit.ly/url-non-special.

Policy updates

New policies

Deprecated policies

  • CopilotCDPPageContext - Control Copilot with Commercial Data Protection access to page context for Microsoft Entra ID profiles (deprecated)

Obsoleted policies

  • AllowTokenBindingForUrls - Configure the list of sites for which Microsoft Edge will attempt to establish a Token Binding with (obsolete)

Version 129.0.2792.89: October 10, 2024

Fixed various bugs and performance issues.

Stable channel security updates are listed here.

Version 128.0.2739.113: October 10, 2024

Fixed various bugs and performance issues for Extended Stable channel.

Stable channel security updates are listed here.

Version 129.0.2792.79: October 3, 2024

Fixed various bugs and performance issues.

Stable channel security updates are listed here.

Version 128.0.2739.107: October 3, 2024

Fixed various bugs and performance issues for Extended Stable channel.

Stable channel security updates are listed here.

Version 128.0.2739.97: September 26, 2024

Fixed various bugs and performance issues for Extended Stable channel.

Stable channel security updates are listed here.

Version 129.0.2792.65: September 26, 2024

Fixed various bugs and performance issues, and feature updates.

Stable channel security updates are listed here.

Feature updates

  • Microsoft Edge sidebar updates. For inactive sidebar users and new Edge users, the sidebar is turned OFF. Users can always return to Settings > Sidebar and turn the sidebar ON again at any time. For active sidebar users, the current sidebar state stays the same.

    Administrators can control the availability of the sidebar using the HubsSidebarEnabled policy.

Version 128.0.2739.90: September 19, 2024

Fixed various bugs and performance issues Extended Stable channel.

Stable channel security updates are listed here.

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.

Note

Portions of this release note are modifications based on work created and shared by Chromium.org and used according to terms described in the Creative Commons Attribution 4.0 International License.

Dev Channel updates

The following Dev channel updates preceded this Stable channel release. The following Dev notes provide detailed information about the changes in each release.

Fixes

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 compatibility 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 wasn't 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 function 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 information, see the CSSWG discussion in GitHub.

    The old and new property names are supported for a few milestones, to help developers migrate to the new position-area name. We're 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.

Policy updates

New policies

Deprecated policies

Version 128.0.2739.79: September 12, 2024

Fixed various bugs and performance issues, improved reliability.

Stable channel security updates are listed here.

Fixes

  • Fixed an issue that caused deployed pinned Shortcuts to the Taskbar to be duplicated.

Improved reliability

  • Fixed a browser crash that occurred when trying to launch a custom protocol from a web page when using the URLAllowlist policy on a managed device.

Version 128.0.2739.67: September 5, 2024

Fixed various bugs and performance issues.

Version 128.0.2739.63: September 3, 2024

Fixed various bugs and performance issues.

Stable channel security updates are listed here.

Fixes

  • Fixed an issue that prevented pages from fully loading when retrieving resources from the HTTP cache and DevTools showed the requests failing with net::ERR_FAILED.

Version 128.0.2739.54: August 29, 2024

Fixed various bugs and performance issues, feature updates.

Stable channel security updates are listed here.

Fixes

  • Fixed an issue that caused custom configured start pages to be stuck in the loading state.

Feature updates

  • Security setting in the Microsoft Edge management service. The Microsoft Edge management service gives admins a dedicated experience to manage specific settings that help improve the security posture of their managed browser instances.

Version 128.0.2739.42: August 22, 2024

Fixed various bugs and performance issues, feature updates, and policy updates.

Important

This update to Stable channel contains a fix for CVE-2024-7971 and CVE-2024-7965, which have been reported by the Chromium team as having an exploit in the wild. For more information, see the Security Update Guide.

Stable channel security updates are listed here.

Dev Channel updates

The following Dev channel updates preceded this Stable channel release. The following Dev notes provide detailed information about the changes in each release.

Fixes

  • Fixed an issue that caused high CPU usage of renderer processes when running Selenium tests and calling driver.quit() to end the testing session.

Feature updates

  • SSE3 Requirement. Microsoft Edge stopped supporting CPUs that lack SSE3. Devices with such CPUs won't receive any more updates. For more information, see Microsoft Edge Supported Operating Systems.

  • Copilot browser Context Policies. The DiscoverPageContextEnabled policy is obsoleted in Microsoft Edge version 128 and doesn't work after Microsoft Edge 127.

    To summarize and answer questions based on browser context in Microsoft Edge, Copilot needs to be able to access the browser context. We're providing two new policies to offer more flexibility for admins to customize Edge browser context access across Copilot chats in Edge sidebar.

    • CopilotPageContext - Control Copilot access to browser context for Microsoft Entra ID profiles.
    • CopilotCDPPageContext - Control Copilot with Commercial Data Protection access to browser context for Microsoft Entra ID profiles.

  • Deprecation of the followable web feature. To improve end user experience, the followable web feature is deprecated. The EdgeFollowEnabled policy is also obsolete.

  • EnforceLocalAnchorConstraintsEnabled policy obsoletion. The EnforceLocalAnchorConstraintsEnabled policy was previously deprecated and is now obsolete in Edge version 128. Since Microsoft Edge 112, constraints in certificates loaded from the platform certificate store are enforced. The EnforceLocalAnchorConstraintsEnabled policy existed as a temporary opt-out in case an enterprise encountered issues with the constraints encoded in their private roots.

  • New Policy for Insecure Downloads over HTTP. Users that download potentially dangerous content on HTTP sites will receive a UI warning in a future Microsoft Edge version. To prepare for this change, the ShowDownloadsInsecureWarningsEnabled policy is now available for admins to enable or disable the warnings related to insecure downloads

  • Edge Bar improvements. Edge Bar, the detachable version of the Edge sidebar in Windows 10, has a changed entry point from the gear icon at the bottom of the Edge sidebar's fly out menu to the edge://settings/sidebar page.

    For Windows 11 and Windows 10 users, clicking the gear icon will now automatically open the edge://settings/sidebar page.

    Also, the ability for Edge Bar to start automatically when starting a Windows 10 device has been enabled again, the Close "X" icon has been moved below the ellipsis menu at the bottom right corner of Edge Bar, and Copilot in Edge will remain within the browser not in Edge Bar. Note: These features are a controlled feature rollout. If you don't see these features, check back as we continue our rollout.

    Disabling Edge Bar through the StandaloneHubsSidebarEnabled policy continues to work, there's a fix to make the UI and briefcase icon appear on the edge://settings/sidebar page coming soon.

Policy updates

New policies

Obsoleted policies

See also