Skip to content

main to live - Apr. 14, 2026 #3776

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
captainbrosset merged 3 commits into from
Apr 15, 2026
Merged

main to live - Apr. 14, 2026 #3776

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
891179e
Bump liquidjs from 10.25.0 to 10.25.5 in /scripts (#3769)
dependabot[bot] Apr 14, 2026
ec751d7
XSLT deprecation in "Site compatibility-impacting changes" (#3775)
captainbrosset Apr 15, 2026
22c81f0
Microsoft Edge 148 web platform release notes (May 2026) (#3772)
captainbrosset Apr 15, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 8 additions & 4 deletions microsoft-edge/toc.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,10 @@
href: ./web-platform/release-notes/index.md
displayName: what's new, announcements

- name: Microsoft Edge 148
href: ./web-platform/release-notes/148.md
displayName: Microsoft Edge 148 web platform release notes (May 2026) # page title

- name: Microsoft Edge 147
href: ./web-platform/release-notes/147.md
displayName: Microsoft Edge 147 web platform release notes (Apr. 2026) # page title
Expand Down Expand Up @@ -66,13 +70,13 @@
href: ./web-platform/release-notes/139.md
displayName: Microsoft Edge 139 web platform release notes (Aug. 2025) # page title

- name: Microsoft Edge 138
href: ./web-platform/release-notes/138.md
displayName: Microsoft Edge 138 web platform release notes (Jun. 2025) # page title

# keep 10 items above
- name: Archive
items:
- name: Microsoft Edge 138
href: ./web-platform/release-notes/138.md
displayName: Microsoft Edge 138 web platform release notes (Jun. 2025) # page title

- name: Microsoft Edge 137
href: ./web-platform/release-notes/137.md
displayName: Microsoft Edge 137 web platform release notes (May 2025) # page title
Expand Down
18 changes: 0 additions & 18 deletions microsoft-edge/web-platform/release-notes/146.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,6 @@ To stay up-to-date and get the latest web platform features, download a preview
* [WebGPU Compatibility mode](#webgpu-compatibility-mode)
* [WebGPU: Texture and Sampler `let` binding](#webgpu-texture-and-sampler-let-binding)
* [WebGPU: Transient attachments](#webgpu-transient-attachments)
* [Always negotiate data channels in WebRTC](#always-negotiate-data-channels-in-webrtc)
* [Populate `targetURL` during file handling](#populate-targeturl-during-file-handling)
* [Stop re-queueing `LaunchParams` on reload](#stop-re-queueing-launchparams-on-reload)
* [Origin trials](#origin-trials)
Expand Down Expand Up @@ -285,23 +284,6 @@ Since the texture contents are discarded after the render pass, the driver might
See also:
* [WebGPU API](https://developer.mozilla.org/docs/Web/API/WebGPU_API) at MDN.

<!-- ------------------------------ -->
#### Always negotiate data channels in WebRTC

The new `alwaysNegotiateDataChannels` option for `RTCPeerConnection` allows you to negotiate data channels in the SDP offer before creating a data channel. The data channel m-line is placed before any audio or video m-lines.

Use this option when creating a peer connection, to ensure that data channels are always negotiated:

```javascript
const pc = new RTCPeerConnection({
alwaysNegotiateDataChannels: true
});
const offer = await pc.createOffer();
```

See also:
* [RTCPeerConnection](https://developer.mozilla.org/docs/Web/API/RTCPeerConnection) at MDN.


<!-- ------------------------------ -->
#### Populate `targetURL` during file handling
Expand Down
101 changes: 1 addition & 100 deletions microsoft-edge/web-platform/release-notes/147.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,6 @@ To stay up-to-date and get the latest web platform features, download a preview
* [`contrast-color()`](#contrast-color)
* [CSS `*-width` properties are now independent of `*-style` properties](#css--width-properties-are-now-independent-of--style-properties)
* [Animation timelines support a `"scroll"` range](#animation-timelines-support-a-scroll-range)
* [`accent-color: auto` now only applies to installed web apps](#accent-color-auto-now-only-applies-to-installed-web-apps)
* [SVG features](#svg-features)
* [`path` attribute on SVG `<textPath>` element](#path-attribute-on-svg-textpath-element)
* [Web APIs](#web-apis)
Expand All @@ -38,23 +37,17 @@ To stay up-to-date and get the latest web platform features, download a preview
* [Connection allowlists](#connection-allowlists)
* [Autofill event](#autofill-event)
* [CSSPseudoElement interface](#csspseudoelement-interface)
* [`dropEffect` handling in drag-and-drop events](#dropeffect-handling-in-drag-and-drop-events)
* [Element-scoped view transitions](#element-scoped-view-transitions)
* [Detect Secure Payment Confirmation capabilities](#detect-secure-payment-confirmation-capabilities)
* [IDNA ContextJ rules](#idna-contextj-rules)
* [`<link rel="modulepreload">` supports JSON and CSS modules](#link-relmodulepreload-supports-json-and-css-modules)
* [Local Network Access restrictions on Service Worker `WindowClient.navigate()`](#local-network-access-restrictions-on-service-worker-windowclientnavigate)
* [Local network access restrictions for WebSockets](#local-network-access-restrictions-for-websockets)
* [Local network access restrictions for WebTransport](#local-network-access-restrictions-for-webtransport)
* [Manifest localization](#manifest-localization)
* [`Math.sumPrecise`](#mathsumprecise)
* [Pointer event suppression on drag start](#pointer-event-suppression-on-drag-start)
* [`pseudoTarget` property on events](#pseudotarget-property-on-events)
* [`Request.isReloadNavigation` attribute](#requestisreloadnavigation-attribute)
* [Respect `autocorrect="off"` for Windows touch keyboard](#respect-autocorrectoff-for-windows-touch-keyboard)
* [Device Memory API limits](#device-memory-api-limits)
* [Web Serial API on Android](#web-serial-api-on-android)
* [Always negotiate data channels in WebRTC](#always-negotiate-data-channels-in-webrtc)
* [WebXR Layers](#webxr-layers)
* [WebXR Plane Detection](#webxr-plane-detection)
* [XML parsing in Rust for non-XSLT scenarios](#xml-parsing-in-rust-for-non-xslt-scenarios)
Expand Down Expand Up @@ -156,19 +149,6 @@ See also:
* [animation-range](https://developer.mozilla.org/docs/Web/CSS/Reference/Properties/animation-range) at MDN.


<!-- ------------------------------ -->
#### `accent-color: auto` now only applies to installed web apps

The `accent-color: auto` CSS property, also known as system accent color, is now scoped to only work within installed Progressive Web Apps (PWAs), not within webpages displayed in the browser. This aligns with the existing `AccentColor` and `AccentColorText` CSS system color keywords.

Previously, when `accent-color` was set to `auto`, form controls would adopt the system accent color in all webpages, whether they're displayed in the browser or in an installed PWA.

This change provides a more consistent developer experience and user experience, while adhering to fingerprinting restrictions.

See also:
* [accent-color](https://developer.mozilla.org/docs/Web/CSS/Reference/Properties/accent-color) at MDN.


<!-- ====================================================================== -->
## SVG features
<!-- https://developer.mozilla.org/docs/Web/SVG -->
Expand Down Expand Up @@ -287,18 +267,6 @@ See also:
* [Pseudo-elements](https://developer.mozilla.org/docs/Web/CSS/Pseudo-elements) at MDN.


<!-- ------------------------------ -->
#### `dropEffect` handling in drag-and-drop events

When using the Drag and Drop API, the `dropEffect` attribute now has the correct predetermined values during `dragenter`, `dragover`, and `dragleave` events, as specified by the HTML standard.

The `dropEffect` is now based on the current `effectAllowed` for `dragenter` and `dragover` events. For `dragleave` events, `dropEffect` is always `"none"`.

See also:
* [HTML Drag and Drop API](https://developer.mozilla.org/docs/Web/API/HTML_Drag_and_Drop_API) at MDN.
* [DataTransfer: dropEffect property](https://developer.mozilla.org/docs/Web/API/DataTransfer/dropEffect) at MDN.


<!-- ------------------------------ -->
#### Element-scoped view transitions

Expand All @@ -310,34 +278,6 @@ See also:
* [View Transitions API](https://developer.mozilla.org/docs/Web/API/View_Transitions_API) at MDN.


<!-- ------------------------------ -->
#### Detect Secure Payment Confirmation capabilities

Use the `PaymentRequest.getSecurePaymentConfirmationCapabilities()` static method to determine which Secure Payment Confirmation features are supported in the browser.

This async method returns an object that describes the browser's Secure Payment Confirmation capabilities. Use the returned object to decide whether to use Secure Payment Confirmation features for your payment flow.

See also:
* [Using Secure Payment Confirmation](https://developer.mozilla.org/docs/Web/API/Payment_Request_API/Using_secure_payment_confirmation) at MDN.


<!-- ------------------------------ -->
#### IDNA ContextJ rules

Microsoft Edge now implements the IDNA ContextJ rules, by disallowing the following characters in most places within URLs:

* ZWNJ (U+200C ZERO WIDTH NON-JOINER)

* ZWJ (U+200D ZERO WIDTH JOINER)

This improves interoperability with other browsers.

IDNA is the mechanism by which non-ASCII characters can occur in domain names. For example, the URL `http://네이버.한국/` is encoded as `http://xn--950bt9s8xi.xn--3e0b707e/`.

See also:
* [Better Unicode support](./143.md#better-unicode-support) in _Microsoft Edge 143 web platform release notes (Dec. 2025)_.


<!-- ------------------------------ -->
#### `<link rel="modulepreload">` supports JSON and CSS modules

Expand Down Expand Up @@ -410,20 +350,6 @@ See also:
* [Math](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Math) at MDN.


<!-- ------------------------------ -->
#### Pointer event suppression on drag start

When a drag operation starts, the browser now sends `pointercancel`, `pointerout`, and `pointerleave` events to the drag source, to indicate that the pointer event stream has ended.

This behavior ensures that the drag source doesn't expect any more events from this pointer during the drag operation.

This behavior is now fully implemented across all platforms.

See also:
* [HTML Drag and Drop API](https://developer.mozilla.org/docs/Web/API/HTML_Drag_and_Drop_API) at MDN.
* [Pointer events](https://developer.mozilla.org/docs/Web/API/Pointer_events) at MDN.


<!-- ------------------------------ -->
#### `pseudoTarget` property on events

Expand Down Expand Up @@ -452,17 +378,6 @@ See also:
* [Request](https://developer.mozilla.org/docs/Web/API/Request) at MDN.


<!-- ------------------------------ -->
#### Respect `autocorrect="off"` for Windows touch keyboard

The Windows touch keyboard now respects the `autocorrect="off"` attribute on editable elements, including `<input>`, `<textarea>`, and `contenteditable` hosts.

Previously, the touch keyboard would autocorrect words even when `autocorrect="off"` was set. Now, autocorrections are detected and reverted when the focused element has `autocorrect="off"`.

See also:
* [autocorrect](https://developer.mozilla.org/docs/Web/HTML/Reference/Global_attributes/autocorrect) at MDN.


<!-- ------------------------------ -->
#### Device Memory API limits

Expand Down Expand Up @@ -493,19 +408,6 @@ See also:
* [Web Serial API](https://developer.mozilla.org/docs/Web/API/Web_Serial_API) at MDN.


<!-- ------------------------------ -->
#### Always negotiate data channels in WebRTC

Use the new `alwaysNegotiateDataChannels` option for `RTCPeerConnection` to negotiate data channels in the Session Description Protocol offer, before creating a data channel.

When enabled:
* The data channel `m=` line is placed before any audio or video `m=` lines.
* When using `BUNDLE`, to reuse a single connection for multiple media types, the data channel `m=` line is used as the offerer tagged media section.

See also:
* [RTCPeerConnection](https://developer.mozilla.org/docs/Web/API/RTCPeerConnection) at MDN.


<!-- ------------------------------ -->
#### WebXR Layers

Expand Down Expand Up @@ -697,7 +599,6 @@ Information about this origin trial:
* [Explainer](https://github.com/webmachinelearning/prompt-api/blob/main/README.md)
* [Feedback](https://github.com/webmachinelearning/prompt-api/issues)
* [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/b7d35247-b855-4b08-b237-89e7a5056117)
* [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/b7d35247-b855-4b08-b237-89e7a5056117)


<!-- ------------------------------ -->
Expand All @@ -720,7 +621,7 @@ Information about this origin trial:
* [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/935893aa-661c-4bf6-9a5e-dc4c4e7ce189)


<!-- ---------- -->
<!-- ------------------------------ -->
#### WebAssembly Custom Descriptors

Expires on Jun. 16, 2026.
Expand Down
Loading
Loading