416973 - firefox remote control cannot use current window

Status: RESOLVED INCOMPLETE

(Core Graveyard :: X-remote, defect)

Description

[Alexander Horz]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.11) Gecko/20071204 Ubuntu/7.10 (gutsy) Firefox/2.0.0.11
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.11) Gecko/20071204 Ubuntu/7.10 (gutsy) Firefox/2.0.0.11

According to http://www.mozilla.org/unix/remote.html, the shell command
   firefox -remote 'openurl(http://mozilla.org)'
should open the specified document without prompting.

The document  is expected to be opened in the current window, since there are specific options for opening in a new tab or a new window, and there is no option for explicit opening in the current window.

(the bug has also been observed in prior 2.0.x versions)

Reproducible: Always

Steps to Reproduce:
(cf. "Additional Information")
Actual Results:  
(cf. "Additional Information")

Expected Results:  
(cf. "Additional Information")

A minor modification of /usr/lib/firefox/components/nsBrowserContentHandler.js
would be sufficient, i.e. modifiyng the single line no 336 from
   var target = nsIBrowserDOMWindow.OPEN_DEFAULTWINDOW;
to
   var target = nsIBrowserDOMWindow.OPEN_CURRENTWINDOW;

(cf. http://www.xulplanet.com/references/xpcomref/ifaces/nsIBrowserDOMWindow.html)

Comment 1

[Alexander Horz]

I've forgotten to explicitely mention that the document is always opened in a new window or a new tab (depends on indidiual preference settings) but not in the current window (as required and expected)

Comment 2

[Alexandre Pereira Nunes]

I can confirm that annoying bug. I'll try the proposed solution.

Comment 3

[Jonathan Mills]

I have this too.  (what I really want is another option, replace-all, which means the new window is the only window open. However the current state just leaves you ever increasing numbers of tabs.

Comment 4

[Benjamin Smedberg]

Mass resolving a bunch of old bugs in the x-remote component in preparation for archiving it. If this bug is still valid and useful, please move it to the "Toolkit: Startup and Profile System" component and reopen it.