browsers.to

Some RSS feeds will show raw code in Chrome from 17 November

Google is removing XSLT, a 1990s technology for styling XML, for security reasons. Edge follows in version 159, and Firefox plans to do the same in 2027.

The Tab Report

2 min read

The short version

What changes
Chrome 158, which starts rolling out on 17 November, stops running XSLT, an old way for sites to turn XML files such as RSS feeds into readable pages.
Who's affected
Mainly people who open styled feeds or older business tools in Chrome, and Edge users once Edge 159 turns it off by default.
What to do
Most readers need do nothing; site owners should move the transformation to their server or add a replacement script, as Google suggests.

Chrome is about to stop turning certain XML files into formatted web pages. The technology behind it, XSLT, dates from the late 1990s, and Google is removing it because the code that runs it is a steady source of security bugs. Most people will never notice. The few who do will open a feed or an old page and see a wall of code.

What changes

Google says XSLT stops working in Chrome 158, which starts rolling out on 17 November, for everyone except sites and companies on two temporary exemptions. XSLT lets a site send a plain data file, such as an RSS feed, with instructions that tell the browser how to display it as a readable page. Without it, Chrome shows the raw file. XML files styled with ordinary CSS are not affected.

Microsoft Edge follows: Microsoft's release notes say XSLT will be off by default in Edge 159. Other browsers built on Chromium, such as Brave, Opera and Vivaldi, usually inherit changes like this; we found no announcement from them.

Why Google is doing it

Google says the libraries that run XSLT are old C and C++ code prone to the kind of memory bugs attackers exploit, and that only about 0.02% of page loads use it. The other engines are heading the same way. Mozilla has announced plans to switch XSLT off in every Mozilla Firefox channel in August 2027, when Chrome's exemptions end, and its published position is that removal "would be good for the long-term health of the web platform". WebKit, the engine behind Safari, said it was "cautiously supportive" in the standards discussion, but hasn't set a date.

Not everyone agrees. In that discussion, developers pointed out that podcast hosts use XSLT so their feeds read like normal pages without any JavaScript. Google's own proposal acknowledged that developer reaction was mostly negative.

What to do

If you just browse, there is nothing to do. If a page you rely on starts showing code, Google points to an extension called "XSLT polyfill" that restores the old behaviour.

If you run a site, Google recommends doing the transformation on your server and sending HTML, or adding a replacement script (a "polyfill") to the page. For feeds, advertise them in your site's HTML so feed readers find them, rather than sending visitors to the raw file. Company IT teams can keep XSLT switched on through a policy while they migrate, until Chrome and Edge 176; Google dates Chrome 176 to August 2027. Google Chrome and Edge follow the same plan because they share an engine, though Edge switches XSLT off two versions later; our Chrome vs Edge comparison covers where they differ.

Sources (6)

  1. 1.Chrome for Developers: Removing XSLT for a more secure browser · 29 October 2025
  2. 2.Microsoft Learn: Microsoft Edge stable channel release notes · 5 November 2026
  3. 3.blink-dev: Intent to Deprecate and Remove: Deprecate and remove XSLT · 24 October 2025
  4. 4.WHATWG: Should we remove XSLT from the web platform? · 1 August 2025
  5. 5.Mozilla standards positions: Removal of XSLT from HTML living standard · 27 August 2025
  6. 6.Mozilla dev-platform: Intent to Unship: XSLT · 26 August 2026