<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Xml on Kuldeep Pisda</title><link>https://kdpisda.in/tag/xml/</link><description>Recent content in Xml on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 18 Oct 2026 08:30:00 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/xml/index.xml" rel="self" type="application/rss+xml"/><item><title>Chrome 158 Stops Running XSLT on November 17, and the Pages at Risk Are Your Raw XML</title><link>https://kdpisda.in/chrome-158-xslt-removal-xml-stylesheet-feeds-sitemaps/</link><pubDate>Sun, 18 Oct 2026 08:30:00 +0530</pubDate><guid>https://kdpisda.in/chrome-158-xslt-removal-xml-stylesheet-feeds-sitemaps/</guid><description>&lt;p&gt;Chrome&amp;rsquo;s &lt;a href="https://developer.chrome.com/docs/web-platform/deprecating-xslt"&gt;XSLT deprecation page&lt;/a&gt; schedules the end of XSLT on Stable for Chrome 158, dated November 17, 2026. Two things go: the &lt;code&gt;XSLTProcessor&lt;/code&gt; JavaScript class, and the &lt;code&gt;&amp;lt;?xml-stylesheet type=&amp;quot;text/xsl&amp;quot; ...?&amp;gt;&lt;/code&gt; processing instruction. The first is easy to find in a code search. The second lives in XML files and templates that nobody has opened in years, and it fails in a way that no automated check will report.&lt;/p&gt;
&lt;h2 id="which-half-breaks-quietly"&gt;Which half breaks quietly&lt;a class="heading-anchor" href="#which-half-breaks-quietly" aria-hidden="true" tabindex="-1"&gt;#&lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;An XML document with an XSLT stylesheet reference is transformed by the browser at load time. The server sends XML. Chrome fetches the stylesheet, applies it, and shows the result. That is why some sites ship a feed or sitemap that looks like a styled page in a browser.&lt;/p&gt;</description></item></channel></rss>