When Facebook tried to use WebP a while back their users didn't like it:
But these days if you really want to use WebP you can use a WebAssembly build of the library to support it in browsers which don't support it natively:
That's just a "Google sucks at UX" issue. Apple recently adopted HEIF in iOS wholesale, but nobody is complaining because they made the correct UX call to convert to JPEG as soon as there's the slightest chance the recipient doesn't support the format.
Firefox (on Mac) lacks three things which I hope they fix them ASAP:
1. Compared to Chrome, FF just makes the Mac insanely hot. Sometimes if a website is stuck at loading, the CPU usage goes seriously high, resulting in temperatures around 80˚ Celsius, and MBP fan rounds at ~5000 rpm.
2. FF doesn't support page scrolling with keyboard shortcuts like Chrome does. On a Mac, you can [big] scroll up/down using alt + arrow keys. "Home" and "End" could also be achieved by Command + arrow keys. On FF however, I haven't found the same shortcuts.
Update: It has a weak form of this feature (but still requires your MBP to have "Home" and "End" buttons on it!):
3. FF used to be faster than Chrome at startup, but now on FF 57-58, when you type in the omni-bar, it takes quite a long time for FF to figure out where it has seen this before. In other words, it can't quickly tab-complete what you're typing among bookmarks, history, etc.
I switched from Chrome to FF a while ago, mostly because of the Quantum and the new slick modern UI. But due to these annoying problems, I switched back to Chrome.
Edit: The comment below mentions another way to achieve Home/End features in FF.
: (warning, autoplaying video) https://www.cnet.com/news/google-mozilla-av1-photo-format-co...
At this point it seems like we might as well wait for the eventual "HEIF for AV1" to get the best bang-for-the-buck implementation if we're going to have to support this format in perpetuity.