414044 - -chrome command line option could be handled in nsDefaultCLH.js

Status: NEW

(Toolkit :: UI Widgets, defect)

Description

[arno renevier]

Hi,
as discussed on bug 322808, comment 8 + on irc, "-chrome" option could be handled in nsDefaultCLH.js to avoid duplicate code (currently in browser/components/nsBrowserContentHandler.js, in suite/browser/nsBrowserContentHandler.js, and in mail/components/nsMailDefaultHandler.js)

A preference would be added, so xulrunner application not wanting to expose that functionnality could disable it.

Comment 1

[arno renevier]

I tried to investigate, but was blocked due to the following difficulty:
nsDefaultCommandLineHandler (in nsBrowserContentHandler.js) is executed before
nsDefaultCLH handler (in nsDefaultCLH.js). So, if I "-chrome" handling code in 
nsDefaultCLH, browser window will open before it has any chance to get 
executed. I don't known if modifying execution order by changing addCategory
argument is the right way to work around that problem.