Slashdot Mirror
What Do You Want On Future Browsers?
Coach Wei writes "An industry wishlist for future browsers has been collected and developed by OpenAjax Alliance. Using wiki as an open collaboration tool, the feature list now lists 37 separate feature requests, covering a wide range of technology areas, such as security, Comet, multimedia, CSS, interactivity, and performance. The goal is to inform the browser vendors about what the Ajax developer community feels are most important for the next round of browsers (i.e., FF4, IE9, Safari4, and Opera10) and to provide supplemental details relative to the feature requests. Currently, the top three voted features are:
2D Drawing/Vector Graphics, The Two HTTP Connection Limit Issue, and HTML DOM Operation Performance In General . OpenAjax Alliance is calling for everyone to vote for his/her favorite features. The alliance also strongly encourages people to comment on the wiki pages for each of the existing features and to add any important new features that are not yet on the list."
On a related note, an anonymous reader writes "The Tao of Mac has put up pretty interesting list of five things that are still wrong with browsers these days, and I have to wonder — with things like AIR starting to be accepted by developers, do we still need the browser at all?"
and a decent h&j algorithm --- if only TBL had taken a closer look at TeXview.app on his NeXT Cube before writing worldwideweb.app
William
Sphinx of black quartz, judge my vow.
I want some degree of protection from the entire browser crashing when a plugin misbehaves(***cough*** flash ***cough***)
I'd like an upload meter.
I know what I want: an upload progress bar. We've had download progress bars for nearly two decades now, so why not the same for uploading? In this age of YouTube and such, users are uploading files in their browsers more often than ever before, and the addition of an upload progress bar in the browser (not implemented as a hackish AJAX/Flash application) would be very much appreciated.
Cyde Weys Musings - Scrutinizing the inscrutable
The important words there are web tasks. I don't want a browser that does e-mail, instant messaging, feed aggregation, balances my check book and feeds my dogs. I want a browser where the unnecessary features have been removed, and those who want them can add them themselves. No add-ons as default, thanks!
Seamonkey works best for me at present -- you can at least choose to install it without all the features, unlike Firefox with comes with the kitchen sink as standard. Which is kind of ironic, considering that Firefox was meant to be the leaner alternative to the Mozilla Suite, and Seamonkey is the continuation of the Mozilla Suite.
I would like firefox to have a "kill the sound" button like IE does. If I'm on a site that plays background music, I can press [esc] in Internet Explorer and get silence. In Firefox, I don't think there is such a keystroke.
When our name is on the back of your car, we're behind you all the way!
Kill 10% of the performance but bounds check everything.
I use "noscript" and flashblocker and I havn't gotten anything yet. but a friend using firefox was trashed by a link a friend sent her. A lot of "legit" sites (esp lyrics) now inject stuff into your computer.
I want safety first, then after that ,, safety. THEN maybe some new feature.
She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
when I first heard of bittorrent, I always thought it would make an excellent addition to the http protocol to utilize bittorrent or something like it to share the content of a page, including embeded images and other media content, for as long as a browser window is open on that page, with the web site itself acting as an initial seed if nobody else is currently viewing the page. Instead of the data transfer load being placed entirely on the web server, the task could be delegated to other machines that are viewing that page, all of which ought to have the information readily available. This would have the upshot of keeping smaller websites from being crippled due to sudden surges in traffic, such as what is all too often caused by news stories on sites such as slashdot and numerous others on the web. Had things gone this way back in the day, I think I can safely say we would not be seeing P2P throttling happening the way it is today, because it would be too prevalently used by the mainstream population for general purpose browsing for the ISP's to pull it off without legitimate complaint from everyday users.
I have to say I'd still like to see something like that... although I suspect now it may be too late, because broadband ISP's are already throttling protocols like bittorrent, so most of its potential benefit may already be gone.
File under 'M' for 'Manic ranting'
Sockets. Raw sockets. Stop pretending with AJAX, with Comet, and just cut to the chase. Why this isn't the first thing on the AJAX agenda beats me.
Sounds like a good wishlist item for future browser: have plugins run as separate process with very limited (or more importantly: well defined) IPC with the browser, probably running as user "nobody." If a plugin crashes, browser crash should not be an option.
In other words, have the browser treat plugins as just as dangerous as data from the 'net.
As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
Right now browsers are limited to linear forward and back. Branching would be nice to see graphically too. Then maybe I wouldn't need so many darn tabs open.
And, the option to open each instance in a seperate process, so one window's crash dosen't take down the rest.