> HOWEVER, in this case (webp), it's likely better to detect it on the server: It would be awesome if this idea could be extended to HTML. I'd love to see cont

> HOWEVER, in this case (webp), it's likely better to detect it on the server: It would be awesome if this idea could be extended to HTML. I'd love to see content negotiation in an Accept header, or some other kind of feature-list header that the browser sends to notify my server of what features it supports. I could then pass that data down to JS or, since the browser already knows that information, why not have a `navigator.features` object that developers can look in and see exactly what is supported? Would eliminate the need for Modernizr or performing your own feature detection...and save a lot of code.