Lue englanniksi Muokkaa

Jaa


Site compatibility-impacting changes coming to Microsoft Edge

This article highlights:

  • High-impact differences between Microsoft Edge and the Chromium project, the browser engine which Microsoft Edge is based on.
  • High-impact web platform changes, which might impact browser compatibility on your site, and which the Microsoft Edge team is tracking especially closely.

For more information about other changes in Microsoft Edge, see Release Notes for web platform for Microsoft Edge.

The web platform is a collection of technologies used for building webpages, including HTML, CSS, JavaScript, and many other open standards. The web platform constantly evolves to improve the user experience, security, and privacy. In some cases, these changes may affect the functionality of existing webpages.

For functionality and compatibility reasons, Microsoft Edge adopts nearly all of the Chromium project's changes to the web platform. However, Microsoft retains full control of the Microsoft Edge browser and may defer or reject changes. The Microsoft Edge team decides if the change benefits browser users.

For information about upcoming Chromium project web platform changes, see Chrome Platform Status Release timeline.

High-impact changes

This table lists high-impact changes which the Microsoft Edge team is tracking closely.

Change Stable channel Experimentation Additional information
WebGPU maxInterStageShaderComponents limit v133 The WebGPU maxInterStageShaderComponents limit is being removed. See Deprecate WebGPU limit maxInterStageShaderComponents.
<link rel=prefetch> five-minute rule v133 Previously, when a resource was prefetched by using <link rel=prefetch>, its cache semantics (specifically, max-age and no-cache) were ignored for the first use within 5 minutes, to avoid refetching. Now, this special case has been removed, and normal HTTP cache semantics are used. See Remove <link rel=prefetch> five-minute rule.
Insecure downloads over HTTP Future release (TBD) When a user tries to download potentially dangerous content from an HTTP site, the user will receive a UI warning, such as "Insecure download blocked." The user will still have an option to proceed and download the item. Admins can use the InsecureContentAllowedForUrls policy to specify HTTP sites for which the warning will be suppressed. Admins can use the InsecureDownloadWarnings feature flag to test the impact of this upcoming feature.
Deprecate unload event Future release (TBD) Introduces a new Permission-Policy to allow creating unload event listeners. The default policy is allow, but the default policy will gradually be migrated to deny, such that unload handlers stop firing on pages, unless a page explicitly opts in to re-enable them. This change is happening in the Chromium project, on which Microsoft Edge is based. For more information, see Intent to Deprecate: Deprecate unload event.
Removal of cross-origin subframe JavaScript dialogs Future release (TBD) Removes window.alert, window.prompt, and window.confirm from cross-origin iframes. This change is happening in the Chromium project, on which Microsoft Edge is based. For more information, see Intent to Remove: Cross origin subframe JS Dialogs.
Deprecate textprediction attribute v133 Removes support for the textprediction HTML attribute, which is a nonstandard attribute that's used to enable or disable the browser-based Text Prediction feature for long-form text inputs. Instead, use the standardized writingsuggestions attribute, which functions similarly to textprediction, but also applies to other writing-assistance features that browsers may provide. Sites that explicitly set textprediction to true or false can instead set writingsuggestions to the same value. For more information, see Writing suggestions in the HTML specification.
Removal of Token Binding support v127, v130 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. The enterprise policy AllowTokenBindingsForUrls will no longer be supported, as of v127. Support for the Token Binding protocol will be removed in v130.
Removal of mutation events v127 Removes support for mutation events in Chromium. Use the MutationObserver API instead. See Intent to Deprecate: Mutation Events.
Removal of Web SQL v124 Fully removes Web SQL support. In prior releases, Web SQL support was disabled by default but could be re-enabled via the WebSQLAccess policy. After this change, there is no longer any mechanism to enable Web SQL support. This change is happening in the Chromium project, on which Microsoft Edge is based. For more information, see Intent to Deprecate and Remove Web SQL.

Notation for browser versions

This article uses the following notation for browser release numbers.

Notation Description
v123 The feature or change ships in Microsoft Edge version 123.
v123 (Chrome+1) The feature or change ships in Microsoft Edge version 123, which is one release after the feature or change ships in Chrome version 122.
v123 (Chrome+2) The feature or change ships in Microsoft Edge version 123, which is two releases after the feature or change ships in Chrome version 121.
Beta v123 The feature or change ships in version 123 of the Beta preview channel of Microsoft Edge.
Dev v123 The feature or change ships in version 123 of the Dev preview channel of Microsoft Edge.
Canary v123 The feature or change ships in version 123 of the Canary preview channel of Microsoft Edge.