Actually this is a non-issue. You could always implement comma separated image fallbacks[1]: background-image: image("wavy.svg", 'wavy.png' , "wavy.gif"); and

Actually this is a non-issue. You could always implement comma separated image fallbacks[1]: background-image: image("wavy.svg", 'wavy.png' , "wavy.gif"); and so on... It seems that Google lowered emphasis on the project, or is still working on it behind-the-scenes. I'd much prefer to have 'less of images' moving over the web (without cutting back on visuals, you know) and save precious bandwidth. [1] http://dev.w3.org/csswg/css3-images/#image-fallbacks http://dev.w3.org/csswg/css3-images/#image-fallbacks And then the fact that Google Chrome has over 30% market share. Makes sense to promote WebP.