Re: user.js ... all hat, no cattle?

Joe Koenig wrote:
> user_pref("dom.disable_window_status_change", true);
> conflicts with many sites. e.g:
> http://www.alltheweb.com/search?q=foo

Those sites should use "title" attribute. The reason the pref is there 
is because status text change is usually not user-friendly. If you don't 
like it, then don't set it. It is off by default.

> user_pref("browser.toolbars.showbutton.print", false);
> user_pref("browser.toolbars.showbutton.search", false);
> 
> didn't work, either.

Chrome settings are saved in localstore.rdf. Button visibilities only 
change when you set them via UI.

> user_pref("plugin.display_plugin_downloader_dialog", false);
> didn't work, either.  I had to delete libnullplugin.so manually.

dunno about this...

> user_pref("browser.turbo.singleProfileOnly", true);
> user_pref("profile.manage_only_at_launch", true);
> 
> were rendered useless when launching a new instance with command line
> parameters. Be it
> mozilla -height 100 -width 100
> or simply
> mozilla -foobar_noneffective

You need to use -remote command. see
http://groups.google.com/groups?selm=bndk2v%24n0s%2403%241%40news.t-online.com

> Are these prefs actually supposed to work, or is this just a some fake
> act of courtesy?  

The prefs you mentioned are hidden preferences.

> I'd just like to know: why is it so hard to _disable_ a /feature/?

Documentation problem. There are 600+ prefs and documentating 'em all is 
no trivial stuff.

> It doesn't end there, of course.  Mozilla's reluctance to adhere
> ~/.Xdefaults  resp. ~/.Xresources is well know, too.  How come, that
> every upcoming toolkit/app seems to consider itself  to be "equipped
> with special rights" or maybe even "bound to establish new standards"?
> Why don't they fscking obey to the user's orders?

dunno what ~/.X***** are. This is what I have for system preferences:

config.use_system_prefs

        Type  Boolean
    Platform  Linux only
Description 	

Specify if the application should use system preferences. System 
preferences are read-only and have higher priority over perferences in 
the user’s profile.

Currently system preferences are available via GConf APIs for Gnome. The 
following table lists five preferences available as system preferences, 
along with the corresponding GConf preference names:

network.proxy.http                    /system/http_proxy/host
network.proxy.http_port               /system/http_proxy/port
network.proxy.ftp                     /system/ftp_proxy/host
network.proxy.ftp_port                /system/ftp_proxy/port
config.use_system_prefs.accessibility /desktop/gnome/interface/accessibility

The default value is false