Firefox 5 is now officially released
mozilla.com
mozilla.com
Although I am not going to install this version on my laptop (I am a chrome guy), I would like to take the opportunity and thank you for the great work you have done for the internet users and web developers.
In the days before firefox+firebug, we were alerting all the way in order to find an undefined / unassigned variable which was causing bugs and terror.
You have made the web a better place, you have made IE a better browser, and I tend to believe, you also made chrome a better browser, and chrome developers work harder by setting the bar that high.
We are now at a time when ALL browsers, including Firefox, are getting better and better thanks in large part to the increasing competition.
It has been a great journey thus far for Firefox. My best wishes to all involved for better and better things in the future.
(Firefox user since v0.6 here. These days I also use Chrome and Chromium quite a lot, especially on Linux, but Firefox remains my main browser.)
I love firefox but have suffered with the memory issues for years. Please free memory when I close tabs, or at least add a flush button so I can reclaim the 500mb it balloons to in a day or two of heavy usage.
http://blog.mozilla.com/nnethercote/2011/05/23/a-better-abou...
In my experience, hitting the GC button rarely makes any detectable improvement. Right at this very moment my Firefox instance is using about 900MB of memory; hitting all three buttons in a row (garbage-collection, cycle-collection, "minimize memory usage") brings the number down to 892MB, ~750MB of which is apparently allocated to "heap-unclassified" and the JavaScript "gc-heap".
Work on reducing Firefox's memory footprint is ongoing; the most recent effort I know of is MemShrink:
http://blog.mozilla.com/nnethercote/2011/03/10/memshrink/
...and it's beginning to make some progress:
http://blog.mozilla.com/nnethercote/2011/06/22/memshrink-pro...
Open standards build the web. Free tools create a vivid creative environment.
With Chrome, my browser automatically updates for stuff like this. I never see it and always have the correct version.
For Firefox, I have to purposefully seek out the next version, and considering I'm still upgrading some of my machines to 4.0 from 3.5 (I downloaded 4.0 yesterday on one machine), this is kind of annoying.
I'm not sure a quick release schedule works quite as well if you've got to manually upgrade. I like Chrome for the same reason I sign up for automatic bill payments - I understand it's important, but I don't want to have to deal with it.
See this article for some of the work we're doing to make add-on compatibility work seamlessly in new versions:
http://blog.mozilla.com/addons/2011/04/19/add-on-compatibili...
I'm running 5.0b7, and have been receiving notifications for a while (maybe 3 days?) that there was an update available; but http://www.mozilla.com/en-US/firefox/channel and https://www.mozilla.com/en-US/firefox/all.html didn't have any upgrade available until today. Is there somewhere else to look, or were my upgrade notifications erroneous?
Depends what you mean by "correct version". If your app isn't tested with 5, then it's not the correct version.
Firefox's release mechanism is the middle ground between IE's and Chrome's: you get updates, but you decide when, and they're not tied to the OS.
People may have felt deterred by this in the past, but I would argue that it has worked impressively well for Chrome so far, and makes older mechanisms seem clumsy and antiquated.
In this era when the unfortunate trend in UI design is to make interfaces easier by making them less functional and less customizable, I also especially want a good look at redesigned major-version updates before I install them
I switched on our super-workstation at the office a couple of days ago for the first time in a couple of weeks. It's a bit of a hungry beast, so only usually switched on when we need the power.
It took more than two hours of me sitting at the workstation to apply all the updates. I had to manually approve more than a dozen different installations, one after another. We used multiple gigabytes of our monthly bandwidth allowance just to download the patches.
This is a recently set up machine, just a couple of months old. Only a carefully chosen set of software is installed, all of it for professional use. Commercial software is all legal. Open source stuff is all recommended versions from master sources/repositories.
I don't like the idea of auto-updates either, certainly not for things that make any sort of functional change. But I have to wonder, if this is the best the modern software world can offer to people who have real work to do, whether auto-updates for security patches and genuine bug fixes aren't worth it.
I also have to wonder whether the world is really a better place now that on-line patching is routinely available. Software companies used to have to get something into a fit state to sell before they started selling it, because patching something afterwards was prohibitively expensive and shipping a product with serious flaws would get you a bad reputation and cost a lot of money.
Where is it that you live that is so resource constrained, in both bandwidth and electricity? And why are you trying to run a business there?
Also it's fair to say that whatever you've saved in electricity has now been decidedly outweighed by the two hours of developer-time you spent updating it.
My home, in the UK.
We actually have a pretty good deal on bandwidth compared to most people here, but wasting several gigs just to download patches every few days is absurd.
The electricity isn't really the issue (though bills for that have risen far above inflation in recent months) but the heat generated by running that machine and all its accompanying peripherals full time is relevant at this time of year.
Besides, why kill the planet pointlessly? A staggering amount of precious resources are wasted because people leave equipment in power-draining stand-by modes all the time these days.
> Also it's fair to say that whatever you've saved in electricity has now been decidedly outweighed by the two hours of developer-time you spent updating it.
Presumably I would have had to spend at least the same amount of time spread out over those two weeks if I'd applied each patch as it became available, probably more because much of the software uses rolled up patch releases so I probably avoided a few intermediate steps.
I think my general point, that the amount and size of downloaded patches in modern software has become absurd, stands.
Frequent updates, if properly managed, are generally a plus: security vulnerabilities get patched before they are widely exploited and minor bugs can be fixed without waiting for a major release. Other than the minor annoyance of downloading and installing frequent updates, I don't see a negative.
Unnecessarily large updates are always negative. If different patching practices would compress a 300 MB update to 15 MB, then there is absolutely no reason to prefer the larger patch. Apple is notorious for this: every software "update" requires downloading an entirely new piece of software (note: this is likely changing in Lion).
Background downloading and patching is a matter of preference. It's something I love in a web browser because of the security updates, but would be much less welcome in professional tools. Since it's a matter of opinion, I don't have much to say here.
The negative is that every time you change the functionality of your software, you risk usability and integration problems. See the way Firefox 5 is repeatedly being slaughtered on Slashdot -- normally a forum that strongly advocates for successful OSS projects -- this week.
I like Chrome's way much better, even though I admit it does play a bit of havoc with the enterprise-y types that don't use standards-compliant sites.
(EDIT: Only when #tabs > 9 it seems. Otherwise all tabs have the "X".)
Unless you're on a flash page, because flash captures your keyboard, because flash hates you.
However there is a bug, clicking the X sometimes causes the need to click it twice because the first time it is ignored.
I havent seen this on linux yet, is it still ugly as all hell or did they improve it like they did with windows version?
Edit: Try it yourself if you disagree.
My guess is that there are more people accidentally closing extra tabs than people who want to close a lot of tabs they haven't seen in a while.
side rant: what's up with search boxes that keep your previous search term in the box. What's the point? iPad does this as well and it drives me insane. I always just manually delete the entry after searching but I shouldn't have to do that and I don't want guests to know my previous search.
[1]: http://support.mozilla.com/en-US/kb/how-do-i-customize-toolb...
On the other hand, if you could make this work, I'd love to see it.
Alternatively, although not intuitive, if the user enters focus with the search bar through a specific key-stroke: CTRL + L for a regular URL entry, and re-route CTRL + K to our web-bar, but with suggestions.
This is an important distinction for privacy, but you are right that we may need to come up with a better UI that unifies the two boxes whilst maintaining the distinction between a local and remote search. The "prospector" series of experimental add-ons from Mozilla Labs have some ideas in this area, most notably AwesomeBar HD: https://mozillalabs.com/prospector/2011/04/27/awesomebar-hd-...
Now, with tabs-on-top, each tab contains its own search box. These should be unique, just like each tab has its own URL bar. It doesn't make sense at all that search queries are preserved between tabs. But that's the way Firefox still does it.
(Thinking about this now, I guess that's a different issue than the one you were talking about... why any search box saves any query after pressing "Enter". Still an annoying little quirk though.)
The location bar is faked, too. Try focusing the location bar and ctrl/cmd+Z-ing through the values it's held since browser startup.
Example: If I search wikipedia and that produces no results, I'll google the same term instead.
That said, it would probably make sense for it to clear out after a few minutes, or after your interaction seems to indicate that you're done with that search term.
Chrome is absolutely unusable for the amount of windows I have open at a time and Firefox doesn't crash on me as much as it used to in order to warrant having every page take up a separate process.
Odd, that's the exact reason I switched from FF to Chrome. I generally have about 20-40 tabs open, and FF is terrible for me with more than just a few open, while Chrome flies along gracefully.
I wonder what the cause for the widely varying performance experiences is?
That damned plugin keep me in FF3, since tree style tabs are so goddamed ugly.
Edit: But looking at the page, it seems the developer posted an update yesterday promising an update in a week or two. yay!
that's always the most important information for me before i upgrade ff, so thank you!
For anyone else who had trouble tracking down modern instructions for this:
* Go to about:flags
* Enable Side tabs (first option)
* Restart Chrome
* Right-click on a tab and chose "Use side tabs"
Not a treeview of collapsible tabs, but muchmuchmuch better than normal tab view in Chrome. Thanks for mentioning that they had this.Enable 'Tab Overview' if you have a Mac with a trackpad.
Three finger swipe down shows all of your tabs like expose.
cd /Applications/Google\ Chrome.app/Contents/MacOS
mv "Google Chrome" "Google Chrome Binary"
echo '#!/bin/bash
exec "${0%/*}/Google Chrome Binary" -enable-vertical-tabs "$@"' > "Google Chrome"
chmod ugo+x "Google Chrome"
This let me start chrome with the "-enable-vertical-tabs" command line switch. Once it was started I needed to right click a tab and choose "Use Side Tabs". /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome -enable-vertical-tabsI believe so, I've been using sidetabs since they were released in Canary one year+ ago and I've never figured out how to get it to work on my Mac
Chrome also just doesn't work well for me for the amount of windows I usually have open at a time. 70+ at least.
By the way, if you are a web developer, I strongly encourage you to use the Firefox Beta or Aurora channel:
Sorry if this sounds harsh, but if you're really expecting a lot of professional web developers to do that, I think you're crazy.
Now that both Chrome and Firefox are on silly release schedules, we waste enough time just keeping up with the breaking changes and random UI rearrangements in day-to-day work. Who has time to spend reading yet another set of release notes every few days, when there's a good chance that nothing in them will be usable in production projects for several years anyway?
If you really want to drive progress, I implore you to stop this madness, and allow a few months for the industry to consolidate so we have some sort of standards to work with. You've made your point: the W3C is a dinosaur chasing a snail riding on a tortoise and you can go faster. But until the new technologies are standard enough that we only have to develop for them once and we can rely on that development still working in a couple of years, all your hard work is being wasted because we still have to write to the lowest common denominator.
You are the new Netscape, Microsoft are the new Microsoft, and now there are several other major browsers we all have to cope with as well. Going it alone just doesn't cut it, whichever of you does it.
Maybe if we were talking about a team of in-house developers responsible for a single application or something it would be more realistic, but not for freelancers or small agencies who get paid time and materials, which seems to be most of us these days if my experience is at all representative.
You have to write to your customers. If your customers are the lowest common denominator I would advice rethinking your business plan.
People around here think it is a perfectly viable business plan to write to only iOS, which has 63 million users, so why isn't a viable business to write only to WebKit (Chrome has 160 million users alone)? And if you write to WebKit it's not much work to make it also work in Firefox and Opera.
The idea that we have to write to the lowest common denominator is the one aspect of web development that I wish would go away. You don't have to, you choose to.
The most popular operating system in the world today is Windows XP, and the most popular browser on Windows XP is Internet Explorer. If you can afford to rule out anyone using IE below version 9, I envy you your business plan, but most of us can't.
It is bad enough that Microsoft creates this problem for us for unrelated commercial reasons. There is no need for the Firefox and Chrome teams to sink to the same level.
> People around here think it is a perfectly viable business plan to write to only iOS
People around here think a lot of things are perfectly viable business plans. Most of them will fail, often because they overlooked some obvious, common sense test they should have considered on day one but didn't.
> The idea that we have to write to the lowest common denominator is the one aspect of web development that I wish would go away. You don't have to, you choose to.
We all wish it would go away, but on my planet the web developer is rarely in a position to determine the requirements of a job for a paying client, nor to dictate the browsing software to be used by the general public. If you are one of the lucky ones, please understand that you in a very small niche. Somehow I doubt the guys working hard on all these new features for Firefox and Chrome and Safari want their work to be useful to only a tiny fraction of the web-using world.
Now there are multiple browsers that are going to modify their rendering engines every few months. Yeah, fuck everything about that. I no longer give even two turds' worth of a care what browsers a particular project works in, as long as it works for me. This is just stupid.
Quite annoying that there isn't an obvious way to get the release notes when browsing to mozilla.com.
Now if only they can polish the Android browser a little more ;)
EDIT: Luckily, I had a moment of intelligence and copied FF4 before installing FF5, so I would recommend doing that if you use S3Fox with any regularity.
https://addons.mozilla.org/firefox/addon/add-on-compatibilit...
1. Open "Documents and Settings\<user name>\Application Data\Mozilla\Firefox\Profiles\<profile>\extensions
2. Find the folder for the unsupported extension, there should be a file called install.rdf inside.
3. Open the file and change the <em:maxVersion> to 5.*.
Might have missed something, but that did the trick for me.
And hence the stupidity in adopting Chrome-style meaningless major version-numbers when what is released is only a minor update. I know the IT industry is highly fashion-driven, but that doesn't mean following fashions doesn't have drawbacks.
This is Firefox 4.1 at best, but released as Firefox 5 with all the needless addon breaking headaches that will bring, just because Mozilla wanted to be more "fashionate". Great job guys. Great job.
I guess this another thing we can thank the Chrome team for.
Point releases in the past have broken extension compatibility, so asking that it be 4.1 instead of 5 wouldn't necessarily have the kinds of tangible benefits that you seem to think it would.
http://blog.mozilla.com/addons/2011/04/19/add-on-compatibili...
It'll also let you report their compatibility back to Mozilla and the extension developers so they know if the extension needs updating.
Update, nope, it does tell you there's an upgrade, though (at least on OS X). I think the next step for the FF team is getting those cool assembly-text-diff things like Chrome has working. Until then, there's just fragmentation.
https://wiki.mozilla.org/Software_Update:MAR
It downloads the update automatically, but it will prompt you to restart a while after the update is downloaded (if you haven't restarted on your own). We are actively working on making the whole process less intrusive and more seamless.
http://dev.chromium.org/developers/design-documents/software... has some of the details. Note the ~90% reduction in size going from bsdiff to this.
I want to use this for my own stuff, because that's cool as hell, but the Courgette source has pretty major dependencies on the rest of Chromium.
Even when update servers aren't dying under heavy load, my internet connection isn't very fast. There are many people who don't have fast connections, both in the US and elsewhere. Programs downloading things in the background render web browsing noticeably slower and make voip unusable. Update size matters.
1. (pdf) http://broadband.cti.gr/el/download/World%20Broadband%20Stat...
2. http://en.wikipedia.org/wiki/List_of_countries_by_number_of_...
Ran Firefox, went to the about window and it was already downloading the update. It also does autoinstall, but you will get notified if you still have the default Vista/7 notification settings (i.e. 'Blah wants to run this. Yes or no').
http://blog.mozilla.com/blog/2011/06/21/mozilla-delivers-new...
Long ago I removed all the navigation buttons from my Firefox toolbar; I much prefer having room for larger URL and search bars.
And a complete list of bug fixes: http://www.mozilla.com/en-US/firefox/5.0/releasenotes/buglis...
Chrome is where I've ended up. If FF ever get the memory leaks straightened out, I may switch back.
That said, my computer has pretty beefy specs, so that may have something to do with it.
I wonder what's the logic behind this release schedule
In general it is always wise to not waste too much time interpreting version numbers, as they often fail to reflect the pace of development that is actually happening. The Linux Kernel has been around forever, but only recently got bumped to 3.0rc1; Chrome on the other hand is already stable at 12.x.
First off, Google rarely even mentions Chrome version numbers in its marketing material, and neither will Mozilla. The http://blog.mozilla.com/ post announcing Firefox 5 does not mention the version number, and neither does the main web site at http://firefox.com/ - also see Chrome's release announcements at http://chrome.blogspot.com/
We actually care much more about delivering features and performance improvements in a timely way than about having a big number before the dot. "Just add one" is a simple rule that saves us from arguing about versions and lets us spend that time improving the browser instead.
Non-technical users rarely even know about version numbers. Meanwhile, people who have any experience in software know that version numbers are and have always been arbitrary. Neither group would be "fooled" by a higher version number, so why would we bother trying?
(Did MacOS really have "more" changes from 8 to 9 than from 10.3 to 10.4, or does Apple just really like the number 10? Did Linux stop getting major changes during the 2.4 series and suddenly start again with the release of 3.0? Is the Solaris 11 release more significant than the SunOS 5.11 release even though they are the same thing? The "real" meaning of a version number has always been whatever the developer wants it to mean.)
The interface wont have as massive changes during faster releases
Previously there were two types of releases: "minor" releases which were installed automatically because they contained security fixes, and "major" releases which prompted the user to choose first.
Now there will be no more "major" or "minor" releases. All new releases will be installed automatically, though I believe there is an exception if any extensions are broken by a new release. (EDIT: I mean, if any extensions that you already have installed will be disabled by the update.)
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGH.
...
Mind if I ask how you guys arrive at decisions like this one? We provide IT support services to individuals & businesses in three counties; automatic updates are, by far, not their favorite thing.
...actually, scratch that, nevermind. We have a new product coming out in six months and I think you just helped us sell it. Big time.
he means silent.
As in, Chrome must be closed, and restarted.
Gosh, wish I had noticed that during the edit window.
Are you talking about extensions that I already have installed or any extension on AMO that might not work with the new version?
It was called Phoenix (0.3 ?) then and was the pinnacle of elegance compared to the uber-crappy IE and bloat-loaded Mozilla. If I remember correctly their policy then was to make every consecutive binary release smaller than previous one.
I'm currently using an Aurora build (what will be Firefox 6), and most of my extensions are already marked compatible.
https://wiki.mozilla.org/Performance/MemShrink
More fixes will be in Firefox 6 and 7, it looks like. Here's a particularly fun bloat fix that should be headed for 7:
http://blog.mozilla.com/nnethercote/2011/06/21/you-make-what...