Linked by Thom Holwerda on Thu 21st Jan 2010 22:22 UTC, submitted by aaronb
Permalink for comment 405382
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2006-03-13
On the surface, not much. I have been using version 3.6 since its first release candidate, and it is closer to its predecessor than any new version of Firefox I have used. Under the hood, you tend to get text loading consistently before images, and the tab you are focused on before those in the background. In general, 3.6 gives the impression of being faster. I understand that it supports some of the newer HTML standards better.
So far, the old extensions and even my themes transitioned fine.
There also is a new tab preview feature that, while not as good as the Tabscope extension, is good enough. Apparently, it causes trouble with Windows 7, so it's disabled by default. Changing "browser.allTabs.previews" to true will put a button on the tab line that you can click on to preview your tabs. Changing "browser.ctrlTab.previews" to true will produce the same previews with a Ctrl-Tab keystroke.
I tend to behave badly toward my browsers. If there is no update to an extension when I want to upgrade, I edit the install.rdf file of the extension I want to keep, and soldier on. You should, of course, never do this.
All in all, it's the kind of upgrade I like: Lots of improvements under the hood, and very little disruption.