uh… I guess I knew y’all were going to remove XSLT but is a user-level error for it really the tact you want to take here? 🥵
0 Boosts
0 Likes
@robinwhittleton @zachleat oh! maybe this is totally my misunderstanding and it's been added by that webpage itself? if it's not being put there by the browser then I have completely misunderstood and you should ignore everything I've said while I go and sit on the step for stupid boys.
If the website themselves are putting a big red user-facing error on a page they own rather than *fixing* it then yeah totally I entirely understand why Zach's questioning it! why would you do that? that's crap!
@sil hmm… I guess I had expected that they would just inject the XSLT JS polyfill clientside. Not ideal but better than this.
@zachleat I have a certain amount of sympathy with the browser team here because… there’s nobody else you can show the error to. A way to have a failing web page email its creator would be fabulous for this but it doesn’t exist. I think what chrome are doing here is bad, I agree. I’m not sure what else they can do. Maybe they should do nothing: that’s about it.
https://www.kryogenix.org/days/2023/01/02/what-to-do-about-hotlinking/ is this same problem from a different angle and I didn’t know what to do about it there either.
as days pass by — What to do about hotlinking