How to stop Firefox from making automatic connections
support.mozilla.org
support.mozilla.org
I have to disable it before I START firefox?? How?
I guess the "easier" way would be to just disconnect your internet, and then install and start Firefox.
That's a bummer.
echo 'user_pref("media.gmp-gmpopenh264.autoupdatemedia.gmp-gmpopenh264.enabled", false);' >> user.js
Preferences set in the user.js file are applied after those in
prefs.js, but are persistent - while the current prefs settings
are saved to prefs.js when Firefox exits, the prefs in user.js
are re-applied on every restart of Firefox - so you would have
to edit user.js to persistently change Firefox' behavior.Thus user.js is handy for knowledgeable users, but could be a bit of a trap for less capable users. ("I can't make it change!")
While I'm on about:config stuff, a handy way to search for config variables is a shortcut:
<DT><A HREF="about:config?filter=%s" SHORTCUTURL="ac">[ac] about:config filter</A>
invoked by putting, say, ac media.gmp
in the address bar.Also to have the old behavior back for soooo many things... like hitting enter in the URL bar actually load the URL even if it didn't change.
browser.urlbar.unifiedcomplete = false
This should bring back the old search bar behaviour so you don't need two keypresses to load a webpage.
In the end, this teaches me much more about controlling the program's behaviour than having developers make decisions for me. But that's just my opinion.
For these users, sub-optimal settings are permanent, so you want to turn everything on.
This is one of the problems with a single program being shared by several demographics.
Firefox needs a button in preferences that says 'enable only connections specifically initiated by the user' - worded better and with appropriate warnings of functionality loss. Or an add-on would be great.
On the one hand, pulling patches automatically protects you from the nasties. On the other hand, it also leaks information off your machine which might not be what you want.
I think a distinction needs to be made for the users.
I understand this reasoning, but I think the pendulum has swung too far from end-user control to a patronizing attitude where we tell users what is good for them - in fact, we decide for them without even telling them.
For example, in this case perhaps some users value confidentiality over system integrity or over performance; Mozilla doesn't empower them to make that decision; the users don't even know that a decision has been made. Mozilla could facillitate end-user control by making the options safe and by explaining them clearly.
There is a balance of course, and I'm just using this issue as a example - it's hardly the most critical.
I don't see how it's patronizing to say, "You can set this the way you want if you care, and people who don't care aren't faced with a bunch of choices they don't want."