Post #2296319

2025-11-10 15:57 UTC

@ki@chaos.social @johl@mastodon.xyz Nobody's getting rid of (corrected: "basically nobody is trying to get rid of") the standard itself, but Google, Apple, and Mozilla are talking about yanking the support for the native rendering engine (and the XSLTProcessor and XSLT processing instruction) from the browsers they make because it's a big chunk of under-policed native functionality that can be replicated in the JS sandbox (or rendered server-side).

Replies (3)

@_O@chaos.social 2025-11-10 16:04

@mark@mastodon.fixermark.com @ki@chaos.social @johl@mastodon.xyz that’s not entirely true see https://github.com/w3ctag/obsoletion/issues/10

Open ##2296320
@bsmall2@fedibird.com 2025-11-11 00:03

@mark@mastodon.fixermark.com @ki@chaos.social @johl@mastodon.xyz Eric Meyer: > I have my own biases around this — some of them in direct conflict with each other! — but my focus here will be on what’s happened so far and what might lie ahead... It’s not hard to see where they got that impression, given some of the things Google has done over the years, but that’s not what’s happening here. Not at this point. I’d like to set some records straight, as an outside observer of both Google and the issue itself. https://meyerweb.com/eric/thoughts/2025/08/22/no-google-did-not-unilaterally-decide-to-kill-xslt/

Open ##2296322
@bohwaz@mamot.fr 2025-11-11 00:58

@mark@mastodon.fixermark.com @ki@chaos.social @johl@mastodon.xyz They could also… write a new rendering engine. I don't known shit, but 90% of Mozilla revenue is from Google, and the whole Webkit development team at Apple is also paid by Google. They literally have billions of dollars but acting like if they had budget constraints.

Open ##2296324