The Secrets of Firefox about:config 263
jcatcw writes "While Firefox is very customizable, many of its settings aren't in the Options. Each setting is named and stored as a string, integer, or Boolean in a file called prefs.js and accessed via about:config from the nav bar. Computerworld provides instructions on 20 tweaks for speeding up page loads, making tabs behave, reducing memory drain, and generally making the interface act the way you want it to. Customization also comes through the must-have FF extensions (but be sure to skip these)."
While it's nice.. (Score:5, Insightful)
Re:While it's nice.. (Score:4, Insightful)
s/Insightful/Redundant/
This is Slashdot: we all think we know we are doing
Re: (Score:3, Informative)
Re:While it's nice.. (Score:5, Insightful)
Re:While it's nice.. (Score:4, Insightful)
Re: (Score:3, Insightful)
Re:While it's nice.. (Score:5, Informative)
From RFC 2616 (HTTP/1.1) [ietf.org] section 8.1.1:
Re: (Score:3, Insightful)
Re:While it's nice.. (Score:4, Informative)
Re:While it's nice.. (Score:5, Informative)
Because some servers violate the protocol by responding incorrectly to pipelined requests. At least, that was the reason 2 years ago.
Re: (Score:2)
That was the reason something like 5 years ago. Or maybe even longer. Browsers have had support for pipelining for quite some time, and it's always been labeled as "experimental". The odd thing about this is, it is always claimed this is a really beneficial optimization, but based purely on what browsers recommend, it appears we are not converging towards ever putting it
Re:While it's nice.. (Score:5, Informative)
RFC 2920 [rfc-editor.org] is the SMTP extension for pipelining. Pipelining is a perfectly valid strategy to reduce the time it takes to send mail by reducing the number of round-trips.
What's rude is violating the RFC that says that certain round-trips are required and the spammers tend to violate those rules (such as asking if a message body can be sent before actually sending it, and waiting for the server's introduction message before the client introduces itself). Pipelining itself is actually quite good.
I won't comment on HTTP pipelining because someone else did already.
Re:While it's nice.. (Score:5, Interesting)
Install Subversion, and use it on your config files.
Subversion: it's not just for projects anymore.
Re: (Score:2, Funny)
Re: (Score:2)
It sure is. They rolled out that old pipelining chestnut on page 5. This crap simply exhausts the maximum number of requests a server can handle more quickly. If the server isn't throttling individual connections (and I don't have one configured which does this) then it's probably a complete waste of time and bandwidth. It also
Re:While it's nice.. (Score:5, Insightful)
Why? He's 100% right! Just follow the instructions and you are all set with no chance of there being problems. You see, the instructions on that web page clearly state in bold letters: "Keep a log of everything you change, or make backups."
So, either:
So, because he is correct, he's a fanboy? With IE, you run the possibility of having to do much more than restore a preferences file if you hose something. With Firefox, if you follow the instructions (and something goes wrong), it takes you a few extra seconds to restore the file to original state and "nothing major" happens (other than a wasted few minutes in total trying the tweaks).
So, if he's a fanboy, what does that make you? Just curious.
Re: (Score:2)
The GGP post wasn't talking about the modifications mentioned in the article, he was talking about about:config changes in general. Obviously, the article isn't going to have "dangerous" about:config tweaks. But then the GP chimed in that more or less no matter what you do, Firefox will handle the changes admirably, which just isn't true. And so, for completely ignoring facts and blindly posting incorrect, positive comments anyway, I said he's a fanboy.
As for the other part of my comment, it's exactl
Re: (Score:2)
Hm. I can only say that if life seems empty, perhaps you could find hobby. I hear those computers can be fun. Oh and look - the sun is shining !
Extensions to Avoid? (Score:5, Insightful)
and their website, so ... (Score:2)
I just want (Score:2, Interesting)
I tried changing every entry that mentions google.com, and sometimes it still queries. WTF!
Re: (Score:2, Interesting)
*NOTE: I don't actually know if you can or not; Google works for me so I've never investigated it.
Re: (Score:2)
Sigh. It's not like you can't change the source code. You know, the source code? That stuff that people are always blabbering about being "open"? Why bother with open source if you don't even take advantage of it for something this simple?
Re: (Score:2)
If open source is for programmers only, than the proprietary software vendor has absolutely nothing to fear from the competition.
Re: (Score:2)
I hate to break it to you, but open source is for programmers. Other people can use it too, obviously, but the general idea, going back to the 70s with RMS, is that programmers can have the code for the programs they use, so they can tailor the software to their specific needs. If you lack the ability to modify the code, there's really no point in even having the code.
In a
Re:I just want (Score:5, Informative)
browser.xul.error_pages.enabled
set it to "true"
Re: (Score:2)
The "set "keyword.enabled" to false" suggestion by "the_cowgod" worked for me though. I didn't see any difference with browser.xul.error_pages.enabled set to true or false.
Re: (Score:3, Informative)
Re:I just want (Score:5, Insightful)
404 is an HTTP status code. If firefox cannot find the server you want to connect to, where do you want that 404 to come from?
Tabs (Score:5, Funny)
Camino? (Score:4, Interesting)
Re:Camino? (Score:4, Informative)
Re: (Score:2)
Did you even bother to try it out? Camino's about:config page is almost identical to FF's page. Any options that are named the same in Camino as in FF will do the same thing. (Camino is just a different front end on Gecko, and about:config options are almost all Gecko options, not browser specific.)
Yes I did bother to try, but not before posting ;) Some of the options are actually not the same at all -- there is no integer preference browser.tabs.closeButtons, for example, which is described in the article. I have actually played with config before in Camino but was baffled by what most of them mean, and had a hard time finding docs describing most of the options.
Re: (Score:3, Informative)
Re: (Score:3, Informative)
http://www.firefoxtutor.com/39/loc-bar-search/ [firefoxtutor.com]
And really, they should have called Iceweasel IreOx, at least until mozilla.org asked them to stop.
Re: (Score:2)
link to one page article (Score:5, Informative)
Re:link to one page article (Score:4, Insightful)
Foons! (Score:5, Informative)
Example: nglayout.initialpaint.delay as 0. This will slow rendering of the page as it causes reflows. Fools.
Re: (Score:2)
Re:Foons! (Score:5, Informative)
Re: (Score:2)
Sometimes I was seeing cases where over 2/3 of all the hits from certain Firefox users were all favicon.ico - which was a 404 error (it's a redirect to bugzilla #120352 now). It was never other browsers, always Firefox.
Re: (Score:2)
Re:Foons! (Score:4, Informative)
Re: (Score:3, Informative)
Example: nglayout.initialpaint.delay as 0. This will slow rendering of the page as it causes reflows. Fools.
From the article, just below the section on nglayout.initialpaint.delay:
Reduce the number of reflows
When Firefox is actively loading a page, it periodically reformats or "reflows" the page as it loads, based on what data has been received. Create a content.notify.interval integer preference to control the minimum number of microseconds (millionths of a second) that elapse between reflows. If it's not explicitly set, it defaults to 120000 (.12 of a second).
Too many reflows may make the browser feel sluggish, so you can increase the interval between reflows by raising this to 500000 (500,000, or 1/2 second) or even to 1000000 (1 million, or 1 second). If you set this value, be sure to also create a Boolean value called content.notify.ontimer and set it to true.
Seems like setting nglayout.initialpaint.delay to 0 and bumping up the reflow interval can get you the page quicker and avoid too many reflows.
A bigger question (Score:5, Insightful)
Re:A bigger question (Score:5, Interesting)
Re: (Score:2, Interesting)
Re: (Score:2)
The article I found didn't really hype the changes as hacks, more just taking advantage of broadband connections - as firefox is (apparently) by default configured for dialup.
Re:A bigger question (Score:5, Funny)
Re: (Score:2)
Re: A bigger question (Score:5, Insightful)
FWIW, I used to change some stuff and it would be back to the default next time I started the broweser. Ditto if I changed it in the config file. It finally took when I changed it in the GNOME configuration manager; I guess it was masking the application-specific configs.
official mozilla reference (Score:5, Informative)
Why aren't these real options? (Score:5, Insightful)
The notebook I'm using right now has this amount of memory, and was easily available in stores 1 year ago. Last time I checked, a web browser should never require the absolute latest system for day-to-day operations (which include having another application in the background, such as a word processor or even MSVC 2005.)
Re: (Score:2)
Re: (Score:3, Interesting)
Re: (Score:2)
Re: (Score:2)
Want to see something funny? Read /. in Opera with the new discussion system turned on.
(Opera slows down so much that it becomes nearly unusable.)
Re: (Score:2)
Re: (Score:2)
My system has 3GB memory. Within a few hours of my typical usage of Firefox, the process has balooned to over 512MB in size. If it remains unchecked (i.e., it sits idle overnight), it beco
Re: (Score:2)
http://kb.mozillazine.org/Browser.sessionhistory.
You could try searching for such settings and turning them back down 1-gig-of-ram levels.
Re: (Score:2)
a little OT kinda, but the video downloader ext... (Score:3, Informative)
In fact, it seems to me that when it doesn't work, "service not available" only happens when I don't watch it first, not in my cache.
Tee Hee (Score:2, Funny)
Re: (Score:2)
Re: (Score:2, Informative)
The Art of Performance Tuning -- a Fable (Score:5, Funny)
A long time ago, when computers remembered using little donuts made of rust, I worked on on a mainframe computer system (CP/V) that supported batch, timesharing, realtime, the works. It had performance monitoring tools, and a large basketload of parameters for sys admins to twiddle.
One of our favorite parameters was SL:BB, documented as batch bias, an input to the process scheduler. When someone called or wrote to us saying they were having problems with performance tuning, we usually suggested they redo their tests varying the setting of SL:BB and let us know what happened. Try different values, 0, 1, 5, 20, 50, 100, things like that. Try it and get back to us.
And lo, they would go off and redo performance runs, and report back.
And we would collect their results and go and muse over them, usually over beer.
SL:BB told us a lot about the user, because SL:BB was a knob that wasn't connected to anything. Oh, the value was range-checked by the parameter setting tool, and dutifully stored in memory, and displayed on performance displays, but it didn't change system performance in any way at all.
That's not what the documentation said, but who believes documentation? We had plans for SL:BB, we just hadn't gotten around to writing the code yet.
So if the user reported that setting SL:BB to 25, but not 24 or 26 gave them incredibly better (or worse) results, we definitely factored that into our analysis.
Those that reported back that the setting of SL:BB didn't make a damn bit of difference, and there were some, we honored as brothers, took into our confidences, and shared beer with at the soonest opportunity. Their bug reports and feature requests received far more attention, for they had passed an important test.
And how many of these Firefox parameters are like SL:BB?
Re: (Score:2)
Re:The Art of Performance Tuning -- a Fable (Score:4, Informative)
Hee.
Re: (Score:2)
Re: (Score:2)
There's browser.cache.memory.capacity which many people swear "fixes Firefox's memory leak." If you look at the instructions on sites, you'll see suggested values ranging from 16384 [freerepublic.com] to 65000 [blogspot.com]. For systems with less than 1 GB of RAM, any of those settings will only increase memory use for Firefox 2 [mozillazine.org]. Obviously, anyone who says that setting fixes a memory leak were imagining the problem to being with (or were causing it in the first place with an absurdly
Re: (Score:2)
Never heard of it, and it's a damn lie that I worked in the mail room for a few years.
Although It's amazing what you can pick up when you read other people's work-delivered magazines though, or have total access to all areas including watching large computers built from the ground up. Can give a punk kid big ideas, that.
Re: (Score:3, Funny)
Re: (Score:2)
Re: (Score:3, Insightful)
Re: (Score:2)
Re: (Score:3, Insightful)
The guy's job was obviously to look at the performance of the system and help users out when they had problems. They might be IT users, but system performance isn't their area. In this context they are end users even if they are also programmers. They just aren't specialists in what this guy does, and it's not their job to do his specialised job on top of theirs.
Trust
Still can't turn off favicons in the bookmark menu (Score:2)
Guess which one of the billion or so features in the UI I can't turn off? I can use about:config to remove them from the URL bar, and the tool bar, where t
userChrome.css (Score:2, Informative)
display: none !important;
}
Re: (Score:2)
Re:Still can't turn off favicons in the bookmark m (Score:5, Informative)
In Firefox 2.0.3, I opened up the DOM inspector, chose the main window, and started drilling down in to the element tree: I found the icons which you loathe.
Open up userChrome.css (in your profile: [profile dir]/chrome/).
In it, the following CSS rule should work to hide the icons:(This selector appears in chrome://browser/skin/browser.css, if you know where that is).
Re: (Score:2)
kdawson... (Score:2, Insightful)
Re: (Score:2)
Funnily enough I saw this [mozillazine.org] just today.
Hacking Firefox (Score:5, Insightful)
Re: (Score:2, Interesting)
Thunderbird also... (Score:4, Informative)
great timing, I needed this article today... (Score:2)
Re: (Score:2)
Opera Version (Score:4, Informative)
"Be sure to skip these" (Score:2)
Computerworld actually had the gall to suggest switching to blocking software that's more selective, allowing you to cherrypick ads to block "while continuing to support the sites we love by allowing most ads to appear." Oh, what a cynical dearth of principles: block our competitors' ads, but NIMBY!
Nope,
Hidden slashdot tweaks THEY don't want you to know (Score:4, Funny)
Re:Hidden slashdot tweaks THEY don't want you to k (Score:5, Funny)
The real scandal is Firefox's cookie options. (Score:2)
One must wonder
Delete all cookies when browser is closed (Score:2, Interesting)
How many do you actually need cookies for? Right. A handful.
The default behaviour, given how the technology is abused these days, should be to delete all cookies and purge the cache when the browser closes - except for the sites specified by the user.
It still irks me that IE (yes, we have to use it at work) still doesn't have an option for 'delete all cookies on exit' - but it is perfectly capable of clearing the rest of the cache.
I agree that the option t
Firefox off track (Score:2, Insightful)
about:config is evidence of feature creep, and hence evidence of Firefox turning into the Mozilla browser.
Past versions of Firefox have added additional features such as image resizing. And guess, what, users are not given the ability to disable this; they must enter into the cryptic about:config.
about:config is an HCI catastrophe.
The only about:config secret I need (Score:2)
Re: (Score:2)
Re:Which option to make the Firehose work again? (Score:5, Funny)
Re:Documentation (Score:4, Informative)
Yes.
MozillaZine Knowledge Base Article on about:config entries [mozillazine.org]
It is the first page Google finds when you search for "about:config". I'll let you decide whether that's easy to find.
If there wasn't, you'd be able to put it in the Knowledge Base yourself.