This is Mozilla's roundabout way of saying that they want to put off starting on WebP or JPEG 2000 as long as possible.
According to Google it's about 30% smaller than JPEG: https://developers.google.com/speed/webp/docs/webp_study
It's a massive effort to switch entire industry to a new format for a 30% gain. With a drop-in replacement of libjpeg you can get 10% gain right now.
Also WebP is based on 2006 VP8, which is obsolete now. Chrome ships with VP9 that's further 26% smaller on keyframes.
I haven't heard that brought up as an objection to the format before, though. If it were really a fundamental stumbling block, there are likely ways to adapt the format around it.
[1] https://developers.google.com/speed/webp/faq#what_is_the_max...
Though I'm sure they have their reasons to stay away from an across-the-board superior format. I just wish I knew what they were. Sigh.
That's not hard: they put out a report months ago concluding that the claimed advantages of WebP were in reality slim to nonexistent, and that it could likely be matched and even outperformed by improved JPEG encoders...which is exactly what they're building now.