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.
Looks good. All we need now are for the extension developers to make their extensions Firefox 3.0 friendly.
Jumpstart the tartan drive.
I remember when Firefox first started it was meant to be a faster and more secure replacement for IE. Well, the longer I have been running it (many of you know that I was probably the last Slashdot IE6 holdout for various reasons) the more I realize how slow and awful it can be -- especially the last few versions.
Now, I haven't run the new beta but I looked through the article and some of the past ones that have come up and noticed all this crap about theming, new features, etc, etc, etc but nothing really talks about how much faster it is and how much less memory the program consumes -- especially when it's been open for more than 24 hours on XP.
So, are they going to go back to light, tight, and fast instead of this feature bloat that seems to have prevailed? Yes, it's nice to have bells and whistles but I think that it's just as important to have a browser that doesn't require me to close it and reopen it so that my machine doesn't grind to a halt every other day if I don't.
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).
I've been using Firefox 3 (trunk builds) before Firefox 2 was an official release. I love it.
Whatever happened to:
> Issue one major release every year (Fx 3 in 2007, Fx 4 in 2008, etc.) since it helps drive upgrades and adoption
http://wiki.mozilla.org/Firefox3/Firefox_Requirements#Release_Roadmap
Now my dream is to see a QT brand of Firefox again, perhaps using QT 4's built-in Webkit. Unify Konqueror, Safari and Firefox on one rendering engine and work towards making that the best damned rendering engine out there. They spent nearly two years on the new Gecko rendering engine, and it still isn't as fast as Webkit/KHTML. Firefox has all the features I want for the most part. I'm not saying they should abandon GTK, but they support multiple widgets and toolkits. Someone please give me a QT 4 branch of Firefox and I've be very happy.
http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
One of the most promising and impressive new features in beta 3 is an integrated add-on installer system that allows users to search for and install add-ons from addons.mozilla.org directly through the add-on manager user interface.
Brilliant! Must build from trunk again!
http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
That's nice, they've moved on from pretending it doesn't exist, blaming the user, blaming extensions, blaming plugins, blaming the memory monitor: blaming everything except the code.
However, as someone who routinely sees Firefox use 300MB (up to 100MB already!), I have to ask:
Did they actually fix it?
So they're addressing it. Does what they've done actually solve the problem? Or will I still watch Firefox use up to 500MB during a normal browsing session?
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
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.
That's not a bug, it's a feature. I frequently grab text from the last known addresses without necessarily wanting to go to the page again (E.g. download heavy sites, buggy sites that crash the browser that I need to submit a bug report on.)
Anonymous Coward
Except... the problem with themes which try to emulate the native look and feel of the platform is that it has to be all or nothing; getting even a minor detail wrong can throw off the whole theme. This is even worse on the Mac, where there are a lot of users who are much pickier than average about the look and feel of the UI -- it has to match the native interface, because if it doesn't they're going to notice. And in the provided screenshots, I can already spot ways that the "native" OS X theme doesn't cut it. For example, the screenshot which proudly shows off an Aqua-style select control and button next to a search box also shows those controls using the wrong font and with the text incorrectly placed. If they can't get those details right, they might as well not try to do a "native" theme at all.
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.
That's a user interface paradigm that's decades old now, and just because the bunch of monkeys coding IE think it's fun to throw it out the window doesn't mean it's a good idea. Microsoft has the anti-Midas touch for interfaces these days anyway (cf. Vista generally, that new Office abomination generally, drop-down menus that hide half their contents for no particular reason, etc.). Emulating them would be a terrible idea.
"Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
Fast, really fast.
Don't trust me. Try it.
I'm hoping that they bring forward Tamarin support in Firefox. Any chance of getting fast javascript before Firefox 4?
Yes I do, but how many average users are going to know that? I'd be willing to bet that the Parent didnt even know that...besides, thats only one of many features that its lacking in comparison to Opera, Avant, etc. There isnt much coding invlived to add a context menu on right-click, or even a tooltip saying "Yadda Yada for Yada!"
AARRRGGHH!
Agreed that would drive me nuts.
I suspect it'd make a nice exploit as well...
"Consider how lucky you are that life has been good to you so far. Alternatively, if life hasn't been good to you so far
I'll have to agree that I prefer having to hit enter as I do that quite often. Some of us actually know how URLs work and what they're for. : ) Power to the consumer!
What day is it? Could you please tell me?
The reason I want FF3 is to get whole-page zoom.
http://arstechnica.com/journals/linux.ars/2007/07/27/firefox-3-gets-full-page-zoom
I use a 110 dots per inch monitor. I hate, hate, hate all web pages that were laid out with WYSIWYG design tools, with fonts set to 7 pixels tall and columns also specified as a certain number of pixels wide.
I don't have eagle eyes and I don't like to sit close to my screen. So I have my personal CSS forcing fonts to a minimum size... which makes some pages ugly, and other pages unreadable (depends on how much the page designer hard-coded with pixel sizes). I'm also using the ImageZoom extension to scale up images... which means the scaled images cover up lots of text on many web pages, and fancy graphical navigation buttons often don't match up with their clickable regions.
And I have a 16:10 ratio monitor... which means that often I will read a web site and there will be a narrow strip of text in the center, and tons of wasted space to either side, again because some web designer hard-coded things with pixel counts.
I used to wish that web designers would make sites that can adapt to unusual screen sizes. Well, the WYSIWYG tools aren't going away, so now I just want to zoom my pages.
steveha
lf(1): it's like ls(1) but sorts filenames by extension, tersely
I'm running Firefox 3 (the previous beta, not the latest), and I set max_total_viewers to 1, which should in theory do what you said. Yet I routinely see ~200MB used by Firefox, and on my 512MB machine I need to restart Firefox once a day or so, since a web browser taking up half of my RAM doesn't make for good responsiveness of everything else.
One issue might be memory fragmentation in Firefox, or so I've been told. Perhaps someone who understands this stuff can clarify.
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
Do you know which settings to disable? Usually I don't mind if moving from one tab to the next is a bit slow - I've got lots of CPU, except when Mozilla tries to burn it all, and it's often slow anyway because the machine's busy paging/swapping heavily.
Bill Stewart
New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
Please don't talk as if you're the only person whose opinion matters. I agree with one of your points and disagree with another. Do you care which way round? 'Course not. UI preferences are very subjective, and certainly not life-or-death. Have some respect for others' points of view.
Actually, the perceived performance issues of Firefox mostly stem from the fact it's a single-threaded architecture running on a JavaScript+XML interpreter (XULRunner).
There is indeed only one thread handling the UI and DOM, but there are multiple threads. Network operations, file decoding and so on run in separate threads from the UI. MAking a multithreaded UI is quite hard; note that IE (at least 6, most likely 7 too) does that too, with the difference that you can have separate windows in different processes altogether; but then they can't talk to each other through JS.
The only time this architecture is really a problem ATM is when JS from a page sucks up CPU: it bogs down the whole UI.
Moving to a fully multithreaded architecture is a very hard problem, esp. for such a complicated application, with such complex interactions as a web browser. Every single little thing would have to be synchronised, with big deadlock risks at each turn.
The only possible approach is to divide work among threads such as there is minimal, well understood interactions between them. You can't for example just have one thread per window, because HTML+DOM+JS expect to be able to touch other windows from the same domain. You could divide processes by originating domain; that's what Apprunner does.
But then you have coordinate communication between the windows and the bookmarks, history and so on. Not too hard to do, but has to be weighed against the minimal gain.
Eventually, we will have to take advantage of many-cores CPU. That means that even DOM parsing will have to be multithreaded, for use on ultra low power 256 cores mobile cpus. Robert O'Callahan is working on this. But what you have in this case is a number of related threads with a very limited scope, and precisely defined interactions.
You can read more on these issues at his blog:
Parallel Dom Access
Night of the living threads
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.
"from what I have heard, it has to do with reclaiming used memory....[snip]"
Or, as the parent called it "memory fragmentation"
This space is intentionally left blank
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
1) 100% of the public using browsers that correctly implement CSS. 40% are still using the superbly broken IE6, and FF2 (20%) doesn't implement display: inline-block, which is important for making bordered tabs and such that scale with the size of their fonts.
2) Full SVG support in all browsers. IE has none, the others have a mix of laughable crap.
3) Clients who trust the designer's artistic sense and ability to compat-test on multiple rigs, instead of, say, looking at it on one windows machine in IE6 at 800x600 resolution and complaining "no, we want the text to wrap after this word, not that word".
Sadly, this environment doesn't exist. Sizing things in pixels and limiting the scope of the primary content to 780px wide is STILL the most reliable way to get a consistent appearance that makes clients happy.
SVG doesn't even really exist in any substantive, usable way, so graphics have to be done in pixels. Font sizes are usually scaled to match those sizes. At least all major browsers will let you override that.
This is the environment we have, and trust me the designers aren't any happier about it than you are. I do fluid-width displays every time my clients will let me (~20%), and I always try to make sure the page won't break when the fonts scale. Beyond that, I'm constrained by the tools I've got.
Highres monitors that wide aren't made for having a single window fill the whole workspace. Super-wide columns aren't readable anyway; human eyes prefer text in narrow columns that wrap quickly.
Try tiling your web browser window next to other work windows, or email, or even 2 or 3 browser windows side-by-side. You'll be happier.
I stole this sig from someone cleverer than me.