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?"
Firefox 3 does support mixed SVG and XHTML. I think the other non-IE browsers do as well.
The shareholder is always right.
Agree with sibling post. The only time any FF install I've got crashes it's the Linux one, whenever I try to kill a flash video before the system is done processing it.
Otherwise it never blips, and I'm a hardcore tab whore: if I can hit CTRL-T I will.
ad logicam Claiming a proposition is false because it was presented as the conclusion of a fallacious argument.
>What is an ``h&j algorithm''?
hyphenation and justification --- instead of just setting one line at a time, the system should consider the entire paragraph and set it so that all lines are as nice as possible w/ the best possible breaks.
See the Knuth and Plass paper on it:
http://doi.ieeecomputersociety.org/10.1109/SFCS.1979.46
Or look at Knuth's book _Digital Typography_
William
Sphinx of black quartz, judge my vow.
I know that you probably realize this, but the reason for the lack of upload progress is because it's a limitation of the HTTP protocol itself. In order to upload you have to send the data in one big POST request and there's no way, via HTTP, to poll the results on the server.
That's why, currently, upload progress bars are implemented in HTML/javascript/server-side scripting. It requires a server side script to dump the current file size on the server and some javascript to poll the server-side script. In order to get upload progress bars standard in all browsers there would be have to be a standard way, via HTTP, to poll the status of the upload on the server.
So don't blame the browsers solely. To get this feature implemented would require modifications to the servers too. So the best way to get this feature implemented in all browsers (in a widely-accepted, standard fashion) is to call for an addition to the HTTP protocol.
s/Lynx/Elinks/
does that, and also allows me to run Flash 32 bits in a 64 bits Firefox.
I absolutely bet it's your flash-plugin. FF3 dies very often for me, when i walk the history with some flash-sites in between. It dies so hard, that the session becemes useless. on windows and linux.
I recommend trying it with flash disabled (=not loadable my the browser!), and when this helps you know the source.
Any sufficiently advanced intelligence is indistinguishable from stupidity.
FF 2.0 would crash for me about once a week, tops.
I've upgraded to FF3 the day it was released, and I'm yet to see it crash.
Running on Linux (CentOS 5).
I usually have at least 2 windows (about 15 tabs) open all the time. Lots of extensions and such.
Maybe there is something wrong with your Linux install/distro ?
morcego