{ "@context": "https://schema.org", "@id": "https://aggr.aymericbeaumet.com/items/lobste-rs/2026-11-03-death-comes-for-xslt/#webpage", "@type": [ "WebPage", "ArchiveComponent" ], "articleBody": "Last halloween, [Google decided to kill XSLT](https://groups.google.com/a/chromium.org/g/blink-dev/c/CxL4gYZeSJA/m/yNs4EsD5AQAJ). That was not a [unilateral decision](https://meyerweb.com/eric/thoughts/2025/08/22/no-google-did-not-unilaterally-decide-to-kill-xslt/) mind you, Google said “jump” and other browser vendors said “how high?”\n\nIn response, I published my [Intent to Deprecate and Remove Google Chrome](https://dbushell.com/2025/11/01/intent-to-deprecate-and-remove-google-chrome/). A performative declaration of course, I don’t install spyware.\n\nFearing my parody lacked seriousness, I created [XSLT.RIP](https://xslt.rip/) to ensure the developer world was informed of Google’s [death note](https://en.wikipedia.org/wiki/Death_Note). This did the trick, although a [few commenters](https://news.ycombinator.com/item?id=45873434) believed it was satire. There is subtlety to [XSLT.RIP](https://xslt.rip/). The website itself is built with XSLT and when Google kills XSLT they’ll kill my website.\n\nThe web standards process and its stewards (*Big Browser*) used to adhere to a social contract. Backwards compatibility was a major design principle. Under no circumstances do you ever purposefully break the web.\n\n- [“Don’t break the web”](https://www.chromium.org/developers/release-process/#dont-break-the-web)\n- [“Don’t break the web”](https://developer.mozilla.org/en-US/docs/Learn_web_development/Getting_started/Web_standards/The_web_standards_model#dont_break_the_web)\n- [“Don’t break the web”](https://github.com/tc39/how-we-work/blob/main/terminology.md#web-compatibilitydont-break-the-web)\n\nGoogle decided to renege and break the web.\n\n[XSLT.RIP](https://xslt.rip/) will be broken soon and I’ll sit back and watch Google break it. [17 November 2026](https://doctor-seo.net/en/blog/news/chrome-edge-removing-xslt/) appears to be the date of execution. Some Chromium-based browsers have been running a [man-in-the-middle attack](https://en.wikipedia.org/wiki/Man-in-the-middle_attack) by injecting propaganda into XSLT websites.\n\n> This site uses XSLT; that functionality is being removed from this browser very soon. When that happens, this page will likely no longer display correctly. You might be able to install a browser extension that allows you to continue viewing it. Otherwise, you should contact the maintainer of the site for further information.\n>\n> Source: [This site uses XSLT: what Chrome’s banner means](https://xsltplayground.com/blog/chrome-xslt/this-site-uses-xslt-warning/) - XSLT Playground\n\nThis appears to be an `` custom element that fails to render when it violates [content security policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP).\n\n![Two examples of the XSLT warning banner quoted above. The first is white text on a red background, the second is broken default HTML styles.](https://dbushell.com/images/blog/2026/xslt-banner.avif)\n\nTwo examples of the XSLT warning banner quoted above. The first is white text on a red background, the second is broken default HTML styles.\n\nI’m testing on [ungoogled-chromium](https://github.com/ungoogled-software/ungoogled-chromium) so who knows how it’s intended to look.\n\n[The line of death](https://textslashplain.com/2017/01/14/the-line-of-death/) is another “social contract” that Google has forgotten. They’re blaming website owners and acting like questionable purveyors of free public Wi-Fi. This is arrogant and intrusive.\n\n“contact the maintainer of the site” — you broke the web Google, own it at least.\n", "authors": [ "dbushell.com via nytpu" ], "captured_at": "2026-11-04T00:52:13.198927099+00:00", "category": "news", "content_html": "

Last halloween, Google decided to kill XSLT. That was not a unilateral decision mind you, Google said “jump” and other browser vendors said “how high?”

\n

In response, I published my Intent to Deprecate and Remove Google Chrome. A performative declaration of course, I don’t install spyware.

\n

Fearing my parody lacked seriousness, I created XSLT.RIP to ensure the developer world was informed of Google’s death note. This did the trick, although a few commenters believed it was satire. There is subtlety to XSLT.RIP. The website itself is built with XSLT and when Google kills XSLT they’ll kill my website.

\n

The web standards process and its stewards (Big Browser) used to adhere to a social contract. Backwards compatibility was a major design principle. Under no circumstances do you ever purposefully break the web.

\n\n

Google decided to renege and break the web.

\n

XSLT.RIP will be broken soon and I’ll sit back and watch Google break it. 17 November 2026 appears to be the date of execution. Some Chromium-based browsers have been running a man-in-the-middle attack by injecting propaganda into XSLT websites.

\n
\n

This site uses XSLT; that functionality is being removed from this browser very soon. When that happens, this page will likely no longer display correctly. You might be able to install a browser extension that allows you to continue viewing it. Otherwise, you should contact the maintainer of the site for further information.

\n

Source: This site uses XSLT: what Chrome’s banner means - XSLT Playground

\n
\n

This appears to be an <xslt-warning-banner> custom element that fails to render when it violates content security policy.

\n

\"Two

\n

Two examples of the XSLT warning banner quoted above. The first is white text on a red background, the second is broken default HTML styles.

\n

I’m testing on ungoogled-chromium so who knows how it’s intended to look.

\n

The line of death is another “social contract” that Google has forgotten. They’re blaming website owners and acting like questionable purveyors of free public Wi-Fi. This is arrogant and intrusive.

\n

“contact the maintainer of the site” — you broke the web Google, own it at least.

\n", "content_markdown": "Last halloween, [Google decided to kill XSLT](https://groups.google.com/a/chromium.org/g/blink-dev/c/CxL4gYZeSJA/m/yNs4EsD5AQAJ). That was not a [unilateral decision](https://meyerweb.com/eric/thoughts/2025/08/22/no-google-did-not-unilaterally-decide-to-kill-xslt/) mind you, Google said “jump” and other browser vendors said “how high?”\n\nIn response, I published my [Intent to Deprecate and Remove Google Chrome](https://dbushell.com/2025/11/01/intent-to-deprecate-and-remove-google-chrome/). A performative declaration of course, I don’t install spyware.\n\nFearing my parody lacked seriousness, I created [XSLT.RIP](https://xslt.rip/) to ensure the developer world was informed of Google’s [death note](https://en.wikipedia.org/wiki/Death_Note). This did the trick, although a [few commenters](https://news.ycombinator.com/item?id=45873434) believed it was satire. There is subtlety to [XSLT.RIP](https://xslt.rip/). The website itself is built with XSLT and when Google kills XSLT they’ll kill my website.\n\nThe web standards process and its stewards (*Big Browser*) used to adhere to a social contract. Backwards compatibility was a major design principle. Under no circumstances do you ever purposefully break the web.\n\n- [“Don’t break the web”](https://www.chromium.org/developers/release-process/#dont-break-the-web)\n- [“Don’t break the web”](https://developer.mozilla.org/en-US/docs/Learn_web_development/Getting_started/Web_standards/The_web_standards_model#dont_break_the_web)\n- [“Don’t break the web”](https://github.com/tc39/how-we-work/blob/main/terminology.md#web-compatibilitydont-break-the-web)\n\nGoogle decided to renege and break the web.\n\n[XSLT.RIP](https://xslt.rip/) will be broken soon and I’ll sit back and watch Google break it. [17 November 2026](https://doctor-seo.net/en/blog/news/chrome-edge-removing-xslt/) appears to be the date of execution. Some Chromium-based browsers have been running a [man-in-the-middle attack](https://en.wikipedia.org/wiki/Man-in-the-middle_attack) by injecting propaganda into XSLT websites.\n\n> This site uses XSLT; that functionality is being removed from this browser very soon. When that happens, this page will likely no longer display correctly. You might be able to install a browser extension that allows you to continue viewing it. Otherwise, you should contact the maintainer of the site for further information.\n>\n> Source: [This site uses XSLT: what Chrome’s banner means](https://xsltplayground.com/blog/chrome-xslt/this-site-uses-xslt-warning/) - XSLT Playground\n\nThis appears to be an `` custom element that fails to render when it violates [content security policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP).\n\n![Two examples of the XSLT warning banner quoted above. The first is white text on a red background, the second is broken default HTML styles.](https://dbushell.com/images/blog/2026/xslt-banner.avif)\n\nTwo examples of the XSLT warning banner quoted above. The first is white text on a red background, the second is broken default HTML styles.\n\nI’m testing on [ungoogled-chromium](https://github.com/ungoogled-software/ungoogled-chromium) so who knows how it’s intended to look.\n\n[The line of death](https://textslashplain.com/2017/01/14/the-line-of-death/) is another “social contract” that Google has forgotten. They’re blaming website owners and acting like questionable purveyors of free public Wi-Fi. This is arrogant and intrusive.\n\n“contact the maintainer of the site” — you broke the web Google, own it at least.\n", "dateCreated": "2026-11-04T00:52:13.198927099+00:00", "date_created": "2026-11-03T15:19:50+00:00", "date_modified": "2026-11-03T15:19:50+00:00", "date_published": "2026-11-03T15:19:50+00:00", "description": "Comments", "external_url": "https://dbushell.com/2026/11/03/xslt-rip/", "git": { "commit": "20068632b65d2830a2d54f25ca1d90d697bea2c0", "path": "items/lobste-rs/2026/11/2026-11-03-death-comes-for-xslt.md", "permalink": "https://github.com/aymericbeaumet/aggr-instance/blob/20068632b65d2830a2d54f25ca1d90d697bea2c0/items/lobste-rs/2026/11/2026-11-03-death-comes-for-xslt.md" }, "id": "urn:aggr:item:61e510da7a0e5125a42365c3ad170ee8574df5d4", "isBasedOn": { "@id": "https://dbushell.com/2026/11/03/xslt-rip/" }, "mainEntity": { "@id": "https://dbushell.com/2026/11/03/xslt-rip/", "@type": "CreativeWork", "archivedAt": { "@id": "https://aggr.aymericbeaumet.com/items/lobste-rs/2026-11-03-death-comes-for-xslt/#webpage" }, "author": [ { "@type": "Person", "name": "dbushell.com via nytpu" } ], "dateModified": "2026-11-03T15:19:50+00:00", "datePublished": "2026-11-03T15:19:50+00:00", "headline": "Death comes for XSLT", "image": { "@type": "ImageObject", "caption": null, "height": 90, "url": "https://dbushell.com/images/articles/2026-11-03-xslt-rip.png", "width": 160 }, "timeRequired": "PT2M", "url": "https://dbushell.com/2026/11/03/xslt-rip/", "wordCount": 362 }, "name": "Archived snapshot: Death comes for XSLT", "preview": { "alt": null, "color": null, "height": 90, "placeholder": { "data_url": "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAQAAAC1HAwCAAAAC0lEQVR42mNk+A8AAQUBAScY42YAAAAASUVORK5CYII=", "hash": "" }, "url": "https://dbushell.com/images/articles/2026-11-03-xslt-rip.png", "width": 160 }, "reading_minutes": 2, "replicated_at": null, "source": "lobste-rs", "source_name": "Lobsters: Top Stories of the Past Week", "summary": "Comments", "tags": [ "browsers", "web" ], "temporalCoverage": "2026-11-04T00:52:13.198927099+00:00", "title": "Death comes for XSLT", "url": "https://aggr.aymericbeaumet.com/items/lobste-rs/2026-11-03-death-comes-for-xslt/", "word_count": 362 }