[whatwg] Built-in image sprite support in HTML5

> HTTP-level solutions are vulnerable to broken proxies and caches, of which
> there are many. This is why HTTP pipelining doesn't really work.

Yeah I know, but does that mean HTML should work around lack of
features in HTTP? I mean you could say HTML5 is vulnerable to broken
browsers :-)

Received on Monday, 31 May 2010 14:22:28 UTC