On 2/20/26 2:14 p.m., Mason Freed wrote:
On Wed, Oct 29, 2025 at 10:26 AM Mason Freed <[email protected]> wrote:
Generally, we're supportive of removing XSLT. As for the
plan, I think it would be best if we disable this in
Canary as soon as possible (via Finch) to find real
breakages that we may be missing. Further, disabling in
Beta and Dev shortly after to get more data is also good.
LGTM1 for the plan with the above changes. We would like
you to check in with results of Canary / Dev / Beta and
warning steps in 3 months to see how we proceed further.
It's taken a bit longer than I expected, but I'm finally back with the
requested update. I've added console warnings starting in M142 (Oct,
2025), and disabled XSLT completely in all pre-stable channels
(Canary/Dev/Beta) starting in M145 (Dec, 2025). I also published a
blog post
<https://developer.chrome.com/docs/web-platform/deprecating-xslt>,
added XSLT to the enterprise release notes
<https://support.google.com/chrome/a/answer/7679408?sjid=6846925605904529338-NA#upChromeBrsrB142>, and
proactively reached out to several enterprises and public sites. As a
result of that outreach, I've received a grand total of two Chromium
bugs (one <https://crbug.com/465491619> was a bug in Chrome's feature
flag implementation, and one <https://crbug.com/468033854> was a bug
in the polyfill). Both have been fixed. I've also had two other
private contractors (for enterprise/government clients) reach out to
me privately, and those conversations seem to be going well. In both
cases, they are in the process of migrating away from client-side
XSLT. The polyfill repo has also seen strong engagement
<https://github.com/mfreed7/xslt_polyfill/issues?q=is%3Aissue>, with
many issues filed and fixed.
Overall, while the community is definitely feeling some migration
pain, I'm trying to stay on top of it and ensure the polyfill is a
functional replacement.
If the Blink API owners have any questions or concerns, please let me
know. Otherwise, I will stick to the plan
<https://developer.chrome.com/docs/web-platform/deprecating-xslt#timeline_for_chrome>,
targeting M152 to start the deprecation trial, and M155 to disable the
feature by default.
Thanks Mason for the detailed update, and for doing the work to land
this removal safely (or as safe as possible). No concerns with sticking
to the plan.
Thanks,
Mason
Thanks,
Vlad
On Monday, October 27, 2025 at 9:37:51 AM UTC-4 j.j. wrote:
see also
https://github.com/mozilla/standards-positions/issues/1287
--
You received this message because you are subscribed to
the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails
from it, send an email to [email protected].
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/4aa38aaf-702e-41d6-91f1-7ba8b18ff675n%40chromium.org
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/4aa38aaf-702e-41d6-91f1-7ba8b18ff675n%40chromium.org?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the
Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from
it, send an email to [email protected].
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw9BLUzVTz_-ioPp0ie%2Bn3g4gbS4wo5LvC3ZQLbzRzUa%2Bg%40mail.gmail.com
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw9BLUzVTz_-ioPp0ie%2Bn3g4gbS4wo5LvC3ZQLbzRzUa%2Bg%40mail.gmail.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/7b76a766-70cc-4c13-ac5e-984917a400a0%40chromium.org.
