Exactly, that's what i'm looking for. Ok, i'll wait, then

http://mozilla.dorando.at/

This link contains a working keyconfig for FF3. You can change everything with this

The Linux skin, while I think it's the better by a long shot (when it comes to integration and default looks), it's clearly Gnome-based, and of no much use for KDE-based distros.

Yes, VERY gnome-based. I agree, they should have done a KDE skin, or at least made a default theme that's as neutral as possible across all platforms.
I'd actually like to have the "keyhole" buttons in my Linux FF3, but I can't find a skin for it.
Any suggestions?

How can HTTP pipelining be turned on? I missed seeing those instructions.

I'm having no trouble with the version of TabMixPlus mentioned above. Thanks for pointing it out, Marc. 

type "about:config" in the location bar, then enter "network.http" in the search bar, and find pipelining - dunno if a restart is necessary.

Quote from: CGA on June 17, 2008, 10:05 PM

About:config->extensions.checkCompatibility=false

Too dangerous for me, would be easy to accidentally forget about it and end up downloading an old extension that really messed with your browser, then as soon as you turn it off all the old addons stop working. But nice note though, I'll confess i didn't know about it
Ehtyar.

You get a nice warning about the disabled check every time you install extensions, and there is always the uninstall button. Anyways, to each his own.

type "about:config" in the location bar, then enter "network.http" in the search bar, and find pipelining - dunno if a restart is necessary.

Thanks, it worked! I restarted Firefox though, so I can't say if it worked without doing that.

And all the FF 3-only addons. I've found LocationBar^2 and Sage-Too.

Locationbar² (also mentioned by Eóin in the second page) is a curious case, as at first it was discussed to merge it in the main Firefox build, when version 3 was in the planning stages. As you may see, they decided against it, which is understandable as for most users it would be a bit confusing.

Now the history repeats itself with Ctrl-Tab, which is proposed for inclusion in Firefox 3.1. It's also for Firefox 3.x only :)

Downloaded it yesterday and modified the Powermarks.xpi (so that the maxversion is 3.0) so that the Powermarks icons will show up in Firefox 3.

However, on clicking the icon, Powermarks does not run.

Does anyone have a workaround ?

Powermarks is a very competent Bookmarks manager and has been mentioned several times in this forum such as

Multi-browser Bookmark Synchronization Tool and Other Multi-Browser Ideas? - DonationCoder.com
"Powermarks is the best! (http://www.kaylon.com/power.html) it not only synchronises your bookmarks, crossbrowser, also lets you instant searches them, extract tags from them so they're grouped, backup/store them online so you can use them between multiple pcs."
http://www.donationcoder.com/forum/index.php?topic=7926.0

Thanks Lashiec for the cake link....
Very funny

 
    If you look at the T in "the", it's written the same way. It's a cursive T, not a 7, unless it's supposed to read "Love, 7he IE 7eam"


Great, they can't even write a standards-compliant cake.

It will be interesting to to see the new IE

As for themes, I'm learning to live with this.....
I would hate to have to skin, it means things look different when you have to fix friend's computers.

But it really has impressed me, I can open heaps of tabs, and they all open quickly (not load, just open) and don't bog down the system.

And remember about:mozilla
The book of mozilla now says:

Mammon slept. And the beast reborn spread over the earth and its numbers
grew legion. And they proclaimed the times and sacrificed crops unto the
fire, with the cunning of foxes. And they built a new world in their own
image as promised by the
sacred words, and spoke
of the beast with their children. Mammon awoke, and lo! it was
naught but a follower.



from The Book of Mozilla, 11:9
(10th Edition)

Fits in with the cake

Both of these are bad design practices. Extensions should never have to keep updating, especially between minor revs, like on each beta and rc. This is where the open source mentality hurts FF - there's little effort on the part of Mozilla to make sure extensions work, since anyone can go fix them if they want to. At least that's what I feel.

I think it's fine to make breaking API changes in major revisions. Otherwise, you either need to keep old cruddy compatibility code around indefinitely, or lock yourself to a possibly ill-designed API.

After an entire day of performance tweaking, I can finally report my results on FF3.

On the bright side, the Mozilla team has certainly made progress with FF3. Memory usage is not exactly lower, but rather more efficient. In other words, unused memory is quickly returned back to the OS, while FF2 would still 'hold it' for longer, causing the leak. However, the actual usage of memory per page opened is still high, but not prohibitively so. To be fair, with the exception of probably Dillo and Lynx, all decent graphical web browsers do utilize a considerable amount of physical memory. The other main advantage of FF is obviously the plethora of plugins, themes and add-ons available, something any other browser, including IE lacks.

On the "need to be improved" section, I will comment with comparison to Opera, which I consider to be closest competitior to FF. With speed tweaks, the loading time is nearly the same on both browsers. However, Opera wins because its more responsive as a software program. For this test, I tried opening a variety of sites, including Java script heavy ones and those that have poorly written HTML. FF can still be made to 'hang' when trying to render a page. By 'hang', I mean that it stops responding to mouse clicks and I can't even CTRL + TAB to switch to another tab. This is a problem that Opera, and even K-Meleon do not suffer from. Even when unable to render a page, the software program should ideally remain responsive to external commands. This one problem results in FF having an overall sluggish feel on windows. Surprisingly, I do not suffer this problem with FF on Linux, but I did not have any extensions installed on that machine, so perhaps its not the best comparison.

Hence, at the end, my conclusion for now remains the same as it was with FF2 and Opera 9.2 : FF is a slow moving ocean liner packed with hundreds of features and an onboard swimming pool while Opera is a speedy boat with minimum features that can possibly satisfy mainstream users, but not more. Now, if Opera went open source or made it easier to write third party plugins, they can steal more of FF's thunder. But, that seems unlikely at present since Opera is a profit oriented company while Mozilla is a non-profit entity.

And IE is probably the Titanic...

For this test, I tried opening a variety of sites, including Java script heavy ones and those that have poorly written HTML. FF can still be made to 'hang' when trying to render a page. By 'hang', I mean that it stops responding to mouse clicks and I can't even CTRL + TAB to switch to another tab. This is a problem that Opera, and even K-Meleon do not suffer from.

While i appreciate any independent testing on this website, it seems more and more people are posting their "results" with absolutely no details/supporting evidence whatsoever. For example, what sites were the browsers tested on? was the cache empty? were the browsers using pipelining? what addons/widgets were installed? was any 3rd party software present that may have interfered? etc etc.

Ehtyar.