On Mon, Aug 25, 2008 at 07:26:54PM +0200, Philipp Kern wrote: > On Mon, Aug 25, 2008 at 06:43:41PM +0200, Mike Hommey wrote: > > > > Currently, lockPref can only be used from the file defined with > > > > general.config.filename. I ignore the reason. I don't see a reason not > > > > to be able to set lockPrefs in other system preference files, > > > > actually... > > > Funnily I just tried it with Lenny's iceweasel. lockPref worked fine > > > and exactly as expected. > > Yes, this is a "special" feature I added in recent xulrunner ;) > > Nice, thanks. > > > > But neither pref nor defaultPref did what they > > > should do, i.e. specify a system default that is actually used. > > > defaultPref > > > did exactly nothing. pref did a bit: I tried it with > > > startup.browser.homepage, > > > and it showed a blank line in the preferences dialog albeit it was > > > correctly in about:config, and showed an empty page at startup. > > This is because (sadly) browser.startup.homepage is a special > > preference, that needs to point to a file where the pref is set. The > > default is resource:/browserconfig.properties, which points to > > /usr/lib/iceweasel/browserconfig.properties, which contains: > > browser.startup.homepage=http://www.mozilla.org/projects/granparadiso/ > > > > You can try to set it to some file:/// url, but I can't guarantee it > > will work. > > Are there other handlers besides resource that are supported for use in > such preferences? And could one be added for some directory below /etc?
I know for sure chrome:/// works. Note you may be able to use resource:/defaults/syspref to escape and go into /etc/iceweasel/pref, but I'm unsure how .properties files would be considered there... Or maybe file:///etc works ? Please try all these and tell me ;) Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
