Slashdot Mirror
Firefox 3 Beta 3 Officially Released
firefoxy writes "Mozilla has officially released Firefox 3 beta 3. This release includes new features, user interface enhancements, and theme improvements. Ars Technica has a review with screenshots. 'Firefox 3 is rapidly approaching completion and much of the work that remains to be done is primarily in the category of fit and finish. There will likely only be one more beta release after this one before Mozilla begins issuing final release candidates.'"
Although if you have a mac, be sure to install the proto theme. Although if you have a mac, you also should try the latest Webkit build too. Its ridiculously fast.
That is all.
Not that box, apparently there was a notice that appeared when you clicked the star to let you know what the star did (that the page had been bookmarked)... however the notice was both added and removed in nightlies between b2 and b3 (guess it ended up being more annoying than helpful).
FF3 is loads faster than FF2. I find that most slowdowns in FF2 were caused by extensions, but FF3 loaded with extensions is just as fast as FF2 in safe-mode. Which is fast.
Assuming this is a compile from the main trunk, memory usage should be better in this for Windows users. A week ago a ported version of FreeBSD's malloc was checked in. This has much less fragmentation compared to Windows' low-frag heaps which should result in less memory used over time and slightly better performance.
High memory usage is different from memory leaks - every time you open a new tab it stores in ram some of the previous and next pages in ram. So if you do a lot of surfing on different tabs it very quickly goes up to 100MB in ram. You can disable that from the settings but you lose the ultra-quick back and forward capability.
Control is an illusion, order our comforting lie. From chaos, through chaos, into chaos we fly
Firefox is all of (any of) MPL, GPL, and LGPL.
I get them to work by setting extensions.checkCompatibility to false.
A few still refuse to work, but most do.
Now, can someone tell me how to keep my bookmarks always sorted by name? The two extensions I know of that do this job ignore my "don't check compatibility" instructions and still refuse to show up in the menus.
i am a soviet space shuttle
Exactly! You would think there would be some 'legacy plugin support' for people to enable if they so desire.
There is. Install the Nightly Tester Tools plugin. It adds a "Make All Compatible" button in your Add-ons dialog that does pretty much just what it says.
ZuluPad, the wiki notepad on crack
First of all, I would strongly recommend actually uninstalling (completely) and reinstalling Firefox if you want to use this beta. Some apparent conflicts between my extensions for Beta 2 and this install caused some of the weirdest, buggiest behavior I've ever seen in Firefox. Only by wiping my profile and starting from scratch was I able to get tabbed browsing to work correctly.
Secondly, if you're annoyed by the new theme, just switch to Small Icons. It looks fine, except for the slightly annoying "Home" button.
Speaking of the "Home" button, it's on the Bookmarks toolbar now, in case you were wondering. You can move it back where it belongs while in the Customize Toolbar dialog.
So far, I don't see a whole lot to write home about. The new theme is definitely ugly. On the other hand, the beta feels very stable and very, very fast.
List boxes have always been ugly in Firefox. I don't think the theme has any control over this. Buttons look pretty good in 3.0 beta 3, but there are some nasty rendering artifacts on in the tab labels.
I agree with you that the details can make or break the experience. I keep trying to use Emacs shortcuts (Ctrl-A, Ctrl-E, etc.) in this text area, but this isn't a native control.
From what I've seen in the last fifteen minutes, 3.0 beta 3 is a big improvement. I've been pretty frustrated with Safari's performance. I'm not a kung fu memory master, but I do know that top shows up to 400 MB RPRVT and close to 2 GB VSIZE after it has been open for a while, even with only one or two tabs open. Sometimes when I close a tab it hangs indefinitely with a beach ball, so I have to force quit. If Firefox can spare me that annoyance, I'll forgive a few UI quirks.
I'm hoping that they bring forward Tamarin support in Firefox. Any chance of getting fast javascript before Firefox 4?
No, not really. ActionMonkey (the project integrating Tamarin/Spidermonkey as part of Moz2) is not ready yet by a long way. According to the "old" timeline, though, there should be a Firefox 4/Moz2 alpha out in Q2 2008 (though I'm not sure I'd trust any timeline from Mozilla, old or new ;-)
http://wiki.mozilla.org/JavaScript:ActionMonkey
http://wiki.mozilla.org/Mozilla_2
The Linux theme fully honours the theme selection set by GTK+ now. The screenshots shown are with the Pango theme. If you don't like it, change theme in GTK+/GNOME.
First, I can't authorize *just* this extension. I have to authorize every extensions from the site, which is generally not what I want.
You seem to be describing Firefox 2. This has been fixed in Firefox 3; it takes 3 clicks to install an extension now. (The patch was in bug 252830.)
The shareholder is always right.
Mozilla Firefox, Portable Edition 3 Beta 3 was released a few hours after the announcement. It's packaged with a launcher so it runs self-contained so you can use it from a flash drive, iPod, portable hard drive, etc. But it's also handy for trying out the current beta without affecting your local install. You can even run it from your desktop to try it out and then delete it.
It's available from the Mozilla Firefox, Portable Edition 3 Beta 3 homepage.
Portable versions of Firefox, GIMP, LibreOffice, etc
I've never had Firefox use that much CPU, but many of those tabs you closed are still cached in memory (along with each of their histories) so they'll reopen really fast if you Undo Closed Tab. Closing the tabs does not necessarily mean they're going away. Changing this option in your about:config should keep that from happening (I think), but you'll also lose some of your session restore functionality. I have it on, and I've never had any of the problems you and a lot of other people have, but I hope this helps.
How about forever? I've had sessions like that (I do the same thing with Google News myself) that eat up over a gig of RAM and never let it go, even after every tab is closed. One time I closed all my Firefox windows except the download status window just to keep the app running at all, and left it like that for two days -- still no memory released.
Closing that last window of course released all my RAM. Luckily, I have a couple gig available, but its just stupid.
- Michael T. Babcock (Yes, I blog)
Firefox keeps by default ten previously closed tabs in memory. So even if you close 10, you won't get any memory back - because while they don't show up in the tab bar, they're still there, with their forward and back sessions stored in their entirety as well. You can recover closed tabs by hitting Ctrl+Shift+T