Edit

Microsoft Edge 148 web platform release notes (May 2026)

The following are the new web platform features and updates in Microsoft Edge 148, which releases on May 7, 2026.

To stay up-to-date and get the latest web platform features, download a preview channel of Microsoft Edge (Beta, Dev, or Canary); go to Become a Microsoft Edge Insider.

Detailed contents:

Microsoft Edge DevTools

See What's new in DevTools (Microsoft Edge 148).

WebView2

See:

CSS features

The following new Cascading Style Sheets (CSS) features are included in Microsoft Edge.

CSS name-only container queries

A CSS query container can be queried based on its container-name only, and the container doesn't need any container-type set:


Previously, @container required some query in addition to the container-name.

See also:

The revert-rule keyword

The revert-rule keyword rolls back the cascade to the previous rule.

This is similar to how revert-layer rolls back the cascade to the previous layer.

For example:

div { color: green; }
div { color: revert-rule; /* Effectively green */ }

The revert-rule keyword is especially useful in combination with conditionals. The revert-rule keyword allows eliminating the current rule if some condition is not met:

div {
  display: if(style(--layout: fancy): grid; else: revert-rule);
}

See also:

at-rule(): CSS feature detection

The at-rule() function can be used in CSS @supports, to feature-detect support for CSS at-rules.

See also:

text-decoration-skip-ink: all

The text-decoration-skip-ink property now has an all value. This property continues to support auto and none.

  • all - Unconditionally applies ink-skipping to all glyphs, including CJK characters. When using text-decoration-skip-ink: all, if you adjust text-underline-position or text-underline-offset to avoid clashing with CJK glyphs, you can explicitly opt in to ink-skipping for those characters as well.

  • auto - Keeps CJK characters un-skipped. Useful for ideographic scripts. Ink-skipping can produce undesirable visual results for ideographic scripts, at typical underline positions.

  • none - Prevents ink-skipping.

See also:

Web APIs

The following new Web API features are included in Microsoft Edge.

Content type in Resource Timing

The new contentType field on PerformanceResourceTiming holds a string that corresponds to the content type of the fetched resource, as returned by the server.

See also:

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.

For dragenter and dragover events, the dropEffect attribute is now based on the current effectAllowed.

For dragleave events, dropEffect is always "none".

See also:

Extended lifetime shared workers

Set the extendedLifetime option when creating a shared worker, to keep the service worker alive for a bounded time after all client pages close. This technique enables reliable completion of async operations during unload.

See also:

Detect Secure Payment Confirmation capabilities

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

This 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.

This is an async, static method.

See also:

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:

Lazy loading for video and audio elements

Use the new loading attribute of and elements, with a value of lazy, to defer media resource loading until the element is near the viewport.

Syntax:

This matches the existing lazy loading behavior for and