@cuchaz
Okay, it looks like I'm staying on FF 118.2.0 on my Android and Windows devices — the last release to have a preference to disable WebP support, and on 124 on my Linux boxes — on which I could patch the option to disable WebP back in and build it myself, building FF for Android and Windows seems like going into too much trouble.
After 124 my userChrome.css hacks started breaking and I stopped updating — now I see that it's not even worth it. Thanks for bringing this to attention!
@bohwaz
Some think that I go way over the top, but I want to have as little Google in my life as possible. I do not consider it an open format: it only has one widely used implementation — the one developed and wholly controlled by Google.
I don't think we should depend on Google for codecs too, especially ones providing minimal compression benefits.
Now that JPEG XL and AV1 exist — better both compression-wise and in terms of governance, I see no point in adopting either WebP or VP9.
@m0xee
Why disable webp support?
@cuchaz