Re:Google is killing the open web, part 2
by dfabulich on Monday November 17, 2025 @06:50PM
(#45959824)
For RSS/Atom, you put this in the XML, right inside the document element (the <feed> element or the <rss> element):
<script src="https://example.org/script.js"
xmlns="http://www.w3.org/1999/xhtml"></script>
You can also put CSS in there, like this: <style xmlns="http://www.w3.org/1999/xhtml">
* { color: red; }
</style>
Or like this: <link href="https://example.org/style.css"
rel="stylesheet" xmlns="http://www.w3.org/1999/xhtml"/>
Re:Google is killing the open web, part 2
by kuschku on Monday November 17, 2025 @07:45PM
(#45960149)
How's the support for the first option? If that reliably works, I'm gonna stop being angry, as it solved all my needs (and would allow polyfilling xslt anyway)
On second thought, that wouldn't allow me to modify the DOM before it's being parsed, I'd have to wipe the DOM and polyfill the entire page load, right?
Re:Google is killing the open web, part 2
by dfabulich on Tuesday November 18, 2025 @01:53AM
(#45962117)
It works great in Chrome, Safari, and Firefox.
https://github.com/dfabulich/style-xml-feeds-without-xslt
Google has recommended a polyfill for XSLT ever since they announced their plan to remove it. https://developer.chrome.com/docs/web-platform/deprecating-x...
Say I have an XML document that uses XSLT, how do I modify it to apply your suggestion?
I've previously suggested the XML stylesheet tag should allow
which would then allow the script to use the service-worker APIs to intercept and transform the request.But with the implementation available today, I see no way to provide a first-class XSLT-like experience with JS.