You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*[Always negotiate data channels in WebRTC](#always-negotiate-data-channels-in-webrtc)
41
40
*[Populate `targetURL` during file handling](#populate-targeturl-during-file-handling)
42
41
*[Stop re-queueing `LaunchParams` on reload](#stop-re-queueing-launchparams-on-reload)
43
42
*[Origin trials](#origin-trials)
@@ -285,23 +284,6 @@ Since the texture contents are discarded after the render pass, the driver might
285
284
See also:
286
285
*[WebGPU API](https://developer.mozilla.org/docs/Web/API/WebGPU_API) at MDN.
287
286
288
-
<!-- ------------------------------ -->
289
-
#### Always negotiate data channels in WebRTC
290
-
291
-
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.
292
-
293
-
Use this option when creating a peer connection, to ensure that data channels are always negotiated:
294
-
295
-
```javascript
296
-
constpc=newRTCPeerConnection({
297
-
alwaysNegotiateDataChannels:true
298
-
});
299
-
constoffer=awaitpc.createOffer();
300
-
```
301
-
302
-
See also:
303
-
*[RTCPeerConnection](https://developer.mozilla.org/docs/Web/API/RTCPeerConnection) at MDN.
*[`<link rel="modulepreload">` supports JSON and CSS modules](#link-relmodulepreload-supports-json-and-css-modules)
46
42
*[Local Network Access restrictions on Service Worker `WindowClient.navigate()`](#local-network-access-restrictions-on-service-worker-windowclientnavigate)
47
43
*[Local network access restrictions for WebSockets](#local-network-access-restrictions-for-websockets)
48
44
*[Local network access restrictions for WebTransport](#local-network-access-restrictions-for-webtransport)
49
45
*[Manifest localization](#manifest-localization)
50
46
*[`Math.sumPrecise`](#mathsumprecise)
51
-
*[Pointer event suppression on drag start](#pointer-event-suppression-on-drag-start)
52
47
*[`pseudoTarget` property on events](#pseudotarget-property-on-events)
*[Respect `autocorrect="off"` for Windows touch keyboard](#respect-autocorrectoff-for-windows-touch-keyboard)
55
49
*[Device Memory API limits](#device-memory-api-limits)
56
50
*[Web Serial API on Android](#web-serial-api-on-android)
57
-
*[Always negotiate data channels in WebRTC](#always-negotiate-data-channels-in-webrtc)
58
51
*[WebXR Layers](#webxr-layers)
59
52
*[WebXR Plane Detection](#webxr-plane-detection)
60
53
*[XML parsing in Rust for non-XSLT scenarios](#xml-parsing-in-rust-for-non-xslt-scenarios)
@@ -156,19 +149,6 @@ See also:
156
149
*[animation-range](https://developer.mozilla.org/docs/Web/CSS/Reference/Properties/animation-range) at MDN.
157
150
158
151
159
-
<!-- ------------------------------ -->
160
-
#### `accent-color: auto` now only applies to installed web apps
161
-
162
-
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.
163
-
164
-
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.
165
-
166
-
This change provides a more consistent developer experience and user experience, while adhering to fingerprinting restrictions.
167
-
168
-
See also:
169
-
*[accent-color](https://developer.mozilla.org/docs/Web/CSS/Reference/Properties/accent-color) at MDN.
*[Pseudo-elements](https://developer.mozilla.org/docs/Web/CSS/Pseudo-elements) at MDN.
288
268
289
269
290
-
<!-- ------------------------------ -->
291
-
#### `dropEffect` handling in drag-and-drop events
292
-
293
-
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.
294
-
295
-
The `dropEffect` is now based on the current `effectAllowed` for `dragenter` and `dragover` events. For `dragleave` events, `dropEffect` is always `"none"`.
296
-
297
-
See also:
298
-
*[HTML Drag and Drop API](https://developer.mozilla.org/docs/Web/API/HTML_Drag_and_Drop_API) at MDN.
299
-
*[DataTransfer: dropEffect property](https://developer.mozilla.org/docs/Web/API/DataTransfer/dropEffect) at MDN.
300
-
301
-
302
270
<!-- ------------------------------ -->
303
271
#### Element-scoped view transitions
304
272
@@ -310,34 +278,6 @@ See also:
310
278
*[View Transitions API](https://developer.mozilla.org/docs/Web/API/View_Transitions_API) at MDN.
Use the `PaymentRequest.getSecurePaymentConfirmationCapabilities()` static method to determine which Secure Payment Confirmation features are supported in the browser.
317
-
318
-
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.
319
-
320
-
See also:
321
-
*[Using Secure Payment Confirmation](https://developer.mozilla.org/docs/Web/API/Payment_Request_API/Using_secure_payment_confirmation) at MDN.
322
-
323
-
324
-
<!-- ------------------------------ -->
325
-
#### IDNA ContextJ rules
326
-
327
-
Microsoft Edge now implements the IDNA ContextJ rules, by disallowing the following characters in most places within URLs:
328
-
329
-
* ZWNJ (U+200C ZERO WIDTH NON-JOINER)
330
-
331
-
* ZWJ (U+200D ZERO WIDTH JOINER)
332
-
333
-
This improves interoperability with other browsers.
334
-
335
-
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/`.
336
-
337
-
See also:
338
-
*[Better Unicode support](./143.md#better-unicode-support) in _Microsoft Edge 143 web platform release notes (Dec. 2025)_.
339
-
340
-
341
281
<!-- ------------------------------ -->
342
282
#### `<link rel="modulepreload">` supports JSON and CSS modules
343
283
@@ -410,20 +350,6 @@ See also:
410
350
*[Math](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Math) at MDN.
411
351
412
352
413
-
<!-- ------------------------------ -->
414
-
#### Pointer event suppression on drag start
415
-
416
-
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.
417
-
418
-
This behavior ensures that the drag source doesn't expect any more events from this pointer during the drag operation.
419
-
420
-
This behavior is now fully implemented across all platforms.
421
-
422
-
See also:
423
-
*[HTML Drag and Drop API](https://developer.mozilla.org/docs/Web/API/HTML_Drag_and_Drop_API) at MDN.
424
-
*[Pointer events](https://developer.mozilla.org/docs/Web/API/Pointer_events) at MDN.
425
-
426
-
427
353
<!-- ------------------------------ -->
428
354
#### `pseudoTarget` property on events
429
355
@@ -452,17 +378,6 @@ See also:
452
378
*[Request](https://developer.mozilla.org/docs/Web/API/Request) at MDN.
453
379
454
380
455
-
<!-- ------------------------------ -->
456
-
#### Respect `autocorrect="off"` for Windows touch keyboard
457
-
458
-
The Windows touch keyboard now respects the `autocorrect="off"` attribute on editable elements, including `<input>`, `<textarea>`, and `contenteditable` hosts.
459
-
460
-
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"`.
461
-
462
-
See also:
463
-
*[autocorrect](https://developer.mozilla.org/docs/Web/HTML/Reference/Global_attributes/autocorrect) at MDN.
464
-
465
-
466
381
<!-- ------------------------------ -->
467
382
#### Device Memory API limits
468
383
@@ -493,19 +408,6 @@ See also:
493
408
*[Web Serial API](https://developer.mozilla.org/docs/Web/API/Web_Serial_API) at MDN.
494
409
495
410
496
-
<!-- ------------------------------ -->
497
-
#### Always negotiate data channels in WebRTC
498
-
499
-
Use the new `alwaysNegotiateDataChannels` option for `RTCPeerConnection` to negotiate data channels in the Session Description Protocol offer, before creating a data channel.
500
-
501
-
When enabled:
502
-
* The data channel `m=` line is placed before any audio or video `m=` lines.
503
-
* 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.
504
-
505
-
See also:
506
-
*[RTCPeerConnection](https://developer.mozilla.org/docs/Web/API/RTCPeerConnection) at MDN.
507
-
508
-
509
411
<!-- ------------------------------ -->
510
412
#### WebXR Layers
511
413
@@ -697,7 +599,6 @@ Information about this origin trial:
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?v=4&size=40){kind=avatar}
0 commit comments