Skip to content

Does the Chrome XSLT deprecation origin trial work in Microsoft Edge for as long as the XSLTEnabled policy? #3985

Open

Description

Link to the documentation page: https://learn.microsoft.com/en-us/deployedge/microsoft-edge-relnote-beta-channel#version-156043148-october-6-2026

Description of the issue: The linked beta release notes state:

The existing XSLTEnabled policy can explicitly enable or disable XSLT regardless of the browser default. If the policy is not configured, XSLT follows the browser’s default behavior. The temporary XSLTEnabled policy is planned for removal in Microsoft Edge 176 in Summer 2027.

Question: I've found that the Chrome XSLT deprecation origin trial also re-enables XSLT in Microsoft Edge when it is launched with --disable-features=XSLT, which I understand reflects the default behaviour planned for Microsoft Edge 159 Stable.

Chrome's XSLT removal timeline states that both the origin trial and the enterprise policy stop functioning in Chrome 176. Could you confirm whether Microsoft Edge will follow the same approach, with the origin trial continuing to work until Microsoft Edge 176, as the XSLTEnabled policy does? It would be very helpful if the release notes mentioned the origin trial as a supported mitigation next to the policy.

Why this matters: For many solution providers the XSLTEnabled policy isn't a practical mitigation. Users of our solutions come from many different organizations, such as small clinics and practices. Many of them don't have the time, expertise or resources to roll out browser policy, and devices may not be enterprise managed at all. The origin trial can instead be applied once to the site hosting the solution, so all users are covered while configurations that rely on XSLT are migrated away from it. Knowing that the origin trial will last as long as the policy would allow those migrations to be planned with confidence.

Minor suggestion: The notes give the policy removal timeframe as "Summer 2027". Summer falls at different times of year in the Northern and Southern Hemispheres, so Southern Hemisphere readers may read this as around January 2027 rather than mid-2027. Giving a range of months instead would make the timeline clear for everyone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions