Websites are not pixel perfect renditions created by dictates issued from servers, they are streams of information decorated with meta-data that give hints on how the information could be rendered.
http://en.wikipedia.org/wiki/Hypertext
> A browser can not predict the particulars of my design well enough to make those decisions for me.
On the contrary, you are not capable of predicting the context in which the information you supply will be used, so less design is better. If you want pixel perfect eye candy write an application but don't use the web, it's lossy by design, for all you know your information will be presented in an audible rather than a readable form, will be printed out on a printer that does not support colour and/or will be read with a device 10,000 years into the future.
Your design is not relevant, the information is what is relevant.
Note that in the case of content such as 'flash', 'silverlight' and other plug-in related content this is going to be a major problem.
Finally, in the interest of commerce and user experience website owners are free to improve their sites to enhance the experience for their users but they should not be required to get basic functionality working.
if it were a display protocol then we could have kept things a lot simpler, specify display width, height and DPI in the request, get back a compressed image and a bunch of 'hot zones' or 'fields' in response. Such protocols existed and they did not make the cut, the one that did explicitly left the rendering decisions to the client receiving the data.