3 ms·
Another bit of ridiculousness is pinning the removal on Google. Removing XSLT was proposed by Mozilla and unanimously supported with no objections by the rest o
by Analemma_ 11mo ago
Another bit of ridiculousness is pinning the removal on Google. Removing XSLT was proposed by Mozilla and unanimously supported with no objections by the rest of the WHATWG. Go blame Mozilla if you want somebody to get mad at, or least blame all the browser vendors equally. This has nothing to do with Chrome’s market share.
- troupo 11mo agoGoogle are the ones immediately springing into action. They only started collecting feedback on which sites may break after they already pushed "Intention to remove" and prepared a PR to remove it from Chromium.
- hn_throwaway_99 11mo ago> Google are the ones immediately springing into action. You say that like it's a bad thing. The proposal was already accepted. The most useful way to get feedback about which sites would break is to actually make a build without XSLT support and see what breaks.
- basscomm 11mo agoShouldn't the users of the Web also get a say? There's been a lot of blowback on this decision, so this isn't as cut and dried as it's being made out to be
- andsoitis 11mo ago> Shouldn't the users of the Web also get a say? How?
- basscomm 11mo agoUsing the technology and opting in to telemetry, feedback forums, user surveys, newsgroups, letter writing, email campaigns, telnet into a BBS, grass-roots websites, semaphore, Morse code, teletype, fax, etc. Anything is better than nothing, if anyone actually listens to the feedback they get instead of taking it and ignoring it.