On Fri, Aug 18, 2006 at 02:58:54PM +0100, Ryan Cartwright <[EMAIL PROTECTED]> 
wrote:
> Package: firefox
> Version: 1.5.dfsg+1.5.0.6-2
> Severity: normal
> 
> 
> Bugzilla report submitted - see reference <a
> href="https://bugzilla.mozilla.org/show_bug.cgi?id=349152";>349152</a>  
> 
> I have made some changes to a system-wide config file - nsFilePicker.js
> but this bug applies to any file within /usr/lib/firefox/components 
> 
> Whenever I update Firefox these files are overwritten and my changes
> lost - fair enough they are system-wide after all.
> 
> To avoid this I have placed a copy of the file (including the changes)
> in my local ~/firefox/<profile>/components directory - as is the norm when
> making user specific config changes. This file should be detected and used
> overriding the system-wide ones but it is not.
> 
> Thus each time I update Firefox I must make those changes again or copy
> a backup version of my changed file over the freshly installed one - this
> is not a good way to do things!
> 
> NOTE
> The reason I am making the changes is to make firefox stop using it's
> own file/print dialogs and get it to use my preferred window manager ones
> (in my case the KDE dialogs).
> 
> So what I am really after is a local config change that allows me to set
> which dialogs to use. Changing nsFilePicker.js is a workaround and I'm happy
> with it but the local copy being ignored is a pain as I have to repeat my
> changes each time I update Firefox (which is quite a bit when using
> sid!)

You can more than probably write an extension that would modify the menu
items and all necessary xul items that make calls to nsFilePicker so
that it calls yours instead, that can be called myFilePicker, for
example, and can be shipped with your extension.

I don't know how extensions are allowed to mess up around, but it may
even be possible to only change the nsFilePicker registration with
a customized extension...

Mike


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to