Slashdot Mirror
Firefox Beta Touts Advanced Engine, Solves 8 Flaws
nandemoari writes "Mozilla may be this year's winner in the 'browser battles' as they ready the next beta version of their tour-de-force, Firefox 3.1. Mozilla is resolving eight critical vulnerabilities found in the current version of Firefox — a move sure to garner applause from devoted Firefox users.
As this year's crop of new browsers emerges, enhanced features are becoming secondary to one thing: speed. Mozilla is nearly ready to release the next beta version of Firefox 3.1 to the public for testing, and insiders predict that it will outpace even Safari 4, which has been the fastest browser in wide release since its beta began last week." It looks like they also will be upping the next major release to v3.5 to better show the significance of the release.
Right-click is a nightmare on linux platforms (don't know if it affects others, I'm exclusively a linux shop these days).
It randomly follows an action rather than bringing up the menu about one time in ten. Opening up email programs, choosing a new window, bringing up link properties... needs fixing, badly. (Workaround for fellow sufferers - install mouse gestures add-on)
Also it seems really really processor-hungry on one of my machines. Wish I knew why.
I don't really care about the speed. It's already fast enough. I just wish they'd sort out the RAM consumption issue and all the memory leaks. My firefox process is currently using 1.1GB of RAM and I have to restart it about twice a day just to free up some RAM. I've only got about 4 extensions installed and I've tried disabling each of them in turn to ensure the problem didn't lie in an extension.
Interesting how stories spin out differently depending on the browser in question. If it were an IE story, there would be howls of derision that the vulnerabilities existed in the first place and questions about why Microsoft didn't fix them more quickly.
Because Acid3 only tests a small part of CSS compliance. Giving fanboys pretty number to shout about should not be a priority. Also, please don't reply to posts that you are actually not replying to. Replying to the first post is obvious attention seeking.
Ooooooooooooor you could just go to about:config and set browser.urlbar.maxRichResults to 0.
But you know, if aimlessly bitching is your thing, please continue.
Wes
This article sounds like empty hype to me.
I still use Firefox, and will continue to do so for the time being. The reason being adblock and flashblock, exclusively. I am not as happy with Firefox as I was when I first used the 0.8 something version. I feel Mozilla have lost their way. Too much bloat like the awesome bar -- which frankly just does not work for me at all, it's an hindrance, not a help.
I want to use chrome, because of the multithreading. Firefox absolutely needs to have multithreading to compete. It can be a true dog to use if you have tabs that reload in the background.
The second that there is some sort of adblock and flashblock for Chrome I'm gone. No more Firefox for me.
I'm sorry to have to do that. I actually bought the firefox T-Shirt. I was active in the GetFirefox campaign. But now, I use it only because of the extensions.
Please, Mozilla get your act together. Now more useless features that should really be extensions, and get multithreading sorted. I want to be a Firefox fan again.
I loved it from the first time I saw it.
Maybe, just maybe, not everyone hates it. Maybe it's just a vocal minority that hates it. Maybe the 'community' -is- getting input and the problem is that you are going against the community, not them.
"If you make people think they're thinking, they'll love you; But if you really make them think, they'll hate you." - DM
You shouldn't have to dig in about:config to disable a prominent feature.
I concur - the Mighty Mouse is not so mighty, Apple's worst product in a long time. I have the problem you describe in Safari 3 and 4 beta. Plus scrolling down has worn out somehow.
Right clicking on the Mighty Mouse appears to have been designed by someone who only used one-button mice before. You have to pretty much take your fingers off of the mouse and only click on the right side of the mouse. It would have made much more sense to make it signal a right click if the right "button" area of the mouse was being touched, regardless of what's happening on the left. It sucks, and they really should fix it (probably could be done with a firmware update).
As for the scroll ball, I have used the "turn the mouse upside down and run the scroll ball around on your pants leg" method with some success. It only works until you get something inside the scroll ball that won't come out. My primary Mighty Mouse (I have four, two are bluetooth and on the same desk) would not scroll right, and even throwing it at the floor and wall didn't work, so I decided to break the damned thing open.
It's actually not hard to crack the mouse open, if you don't mind breaking that little collar that runs around the bottom of the mouse. There are two flexible connections that you have to disconnect, but you can remove the scroll ball mechanism with a small phillips screwdriver, disassemble it, clean it out, and reassemble it. I did it a month ago with no further problems. There is an order to reassembling the mouse and not having one of the flexible connections pull out, but it's not hard to trial and error your way through.
Putting moderation advice in your