I've heard it said, here and other places, that Opera is the fastest browser available. It is fast - there's no denying that - but there are ways to make FireFox render pages every bit as quickly, with just a few easy "tweaks." I had thought these adjustments were pretty well-known, but it's beginning to seem as though they may not be. So I thought it was worthwhile to bring these "hidden settings" more into the light. To get started, type "about:config" in your FireFox address bar. The settings you're looking for are:
1.) network.http.pipelining
2.) network.http.pipelining.firstrequest
3.) network.http.pipelining.maxrequests
4.) network.http.proxy.pipelining
5.) nglayout.initialpaint.delay
Set #1, #2, and #4 to "true". Set #3 to a high number, like 32. Set #5 to 0.
Enabling the pipelining features allows the browser to make multiple requests to the server at the same time. The "maxrequests" is the maximum number of requests it will send at once. I've heard that 8 is the most it will send at once, but setting it higher won't hurt, just in case. The initialpaint.delay is the length of time (in milliseconds) after the server response before the browser begins to paint the page. Adjusting those settings will help pages render much faster in FireFox. In fact, my own observations have been that, tweaked in this manner, FireFox will render faster than Opera (and yes, I realize that others may experience different results).
Worked allright for me. I had to create a new boolean value for network.http.pipelining.firstrequest and a new integer value for
nglayout.initialpaint.delay
__________________
27
Last edited by Haukur Gudnason; 19-10-2004 at 09:33:PM.
(It doesn't require installing)
And fill the boxes as shown in the screenshot. (near that text written in the foreign language you must put '9' six times as shown in the screenshot, not less not more.)
That's it. very simple, very easy, and it works! Oh, and just incase, create a restore point before you tweak it. This program hasn't messed up anything yet, but you can't be too safe.
"Successful exploitation would normally require that a user is tricked into opening a link from a malicious web site to a trusted web site in a new tab."
Not something you'd do normally, but a bug is always a bug... anyways... where the hell did that come from? don't turn this thread into a Firefox x Opera as I've seen way too many of those...
I'm pretty sure everyone here has chosen their favorite browser and is quite happy with it. If you think any of the major browsers is bug free, you're wrong. Firefox has some, Opera has some and IE has a lot of them
Funnily enough, Firefox has exactly the same bug you reported: