<h2>1. Standard Libraries</h2> I don't think this is necessary.  A browser can download thousands of lines of compressed text in a second. <h2>2. Server Push</h2> I agree with this one, but in order for the server to push, you have to have something running in the browser to handle the incoming data.  I don't know how you would do this in a general way on a browser level.  Everyway I can think of would require some piece of custom code, thus something embedable (like flash, applets, etc.).
<h2>3. Better Widgets</h2> I completely agree with this one most of all.  If we can have standard html elements like text boxes, radio buttons, etc.  Why haven't more advanced structures like trees and the like been invented.  This is an area where browser technology needs to catch up.
<h2>4. Vector Graphics</h2> I'd rather see the browser handle intelligent page scaling.  For instance, if you are running at a very high resolution, I'd like to configure the browser to uniformly scale attributes in .CSS files, html element's width values, image pixels, etc.  It seems like this would be easy to do.  I use ImageZoom, a plugin for Firefox to automaticly scale images, but I'd like to see the style elements automamticly scale as well.
<h2>5. Local Storage</h2>

I don't see a need for this feature.

What did I miss?

1) Print integration!  I'd like to have the browser have some type of "hooks" into it that a web application can use to print directly to a printer rather than having "Printable Views" or some type of embedded active X object hacked together to do this.

1. Not needed. What we need is a standard way to provide SHA-1 hashes so browsers can know that they already downloaded it from a different site. Problem solved.
2. Agreed.
3. Not really needed (see my answer to point 1), but a few nice ones could come in handy.
4. VML sort of gets the job done, but I agree that I'd like to see Canvas and SVG natively supported in IE. (I'd also like to see not just browsers but windowing systems in general support smarter automatic scaling for fine resolution.)
5. See the WHATWG Storage recommendation.
6. Print support in CSS might be enough, but I'm not fully experienced in this area.
7. My own addition: Streaming media. We obviously need it, and having to depend on Flash or Quicktime or whatever is really a big pain. Get some patent-free (or equivalent) thing like Ogg into all browsers and life would get so much easier.

I don't know... I still think that at this point the top ONE feature the browsers need is to become fully standard compliant. Until all the major browsers (especially you-know-which) get "there", trying to bloat browsers with more stuff would only cause more inconsistencies across and make application development _harder_ instead of easier.

I'd like to see pluggable language support. I mean, we have the ability to specify the scripting language in our HTML code, but we don't exactly have much choice of what to actually use. JavaScript is a fine language (although much maligned and poorly understood), but I should be able to write my browser scripts in Groovy or whatever if I so choose.

Just as a note to this blog post, Dojo Storage as of Dojo 0.4.1 now will automagically use native browser storage if it is available, such as on Firefox 2 which implements the WHAT WG Storage spec. More details: http://manual.dojotoolkit.org/WikiHome/DojoDotBook/Book50 Best, Brad Neuberg bkn3@columbia.edu Weblog: codinginparadise.org