- cross-posted to:
- hackernews@lemmy.bestiver.se
- cross-posted to:
- hackernews@lemmy.bestiver.se
cross-posted from: https://lemmy.bestiver.se/post/555312
My comment: It seems google is trying to pull another Manifest v3 and JPEGXL - propose then ignore everyone and do it anyway.
Why not fix library, corporate are lacking of founds to fix all the tickets ? Reminds me of Google openssl fork because it’s not “their” opensource product so they won’t contribute or pay someone to do it.
Looking through the comments, someone already wrote a polyfill that people could use if they need it. It’s a niche feature that is the source of security vulnerabilities, so why fix it if they can safely replace it?