280636 - Starting -remote with new-tab is now broken

Status: RESOLVED EXPIRED

(Firefox :: Tabbed Browser, defect)

Description

[Barry Kauler]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041001 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041001 Firefox/0.10.1

Right now I'm using Firefox 1.0pr1, which does NOT have this bug. Also, Mozilla
1.7.5 does NOT have this bug.
Later versions though, starting the browser from the commandline with 
 -remote "($@,new-tab)"
opens a new window if the browser is already running, not a new tab.

I compiled Mozilla 1.8a5 and Mozilla 1.8a6, both have this bug. Note, I also
compiled the 1.7.5 myself, which does not have the bug. A friend has tested the
official release Firefox 1.0, binary that he downloaded, and it has the bug.
So, something has happened between 1.0pr1 and 1.0 that has introduced this bug.


Reproducible: Always

Actual Results:  
Problem fully described above.

Expected Results:  
Problem fully described above.

Comment 1

[Barry Kauler]

Sorry, I typed it wrong (only in this bug report though!)
It should be:
 -remote "openURL($@,new-tab)"

Comment 2

[daneel]

this is a trivial bug to fix

in the script "firefox", change:

[ `expr "${_optLast}" : '/.*'` -eq 0 ] && _optLast="file://`pwd`/${_optLast}"

to this line:

[ `expr "${_optLast}" : '/.*'` -eq 0 ] && _optLast="file://`pwd`/${_optLast}" ||
_optLast="file://${_optLast}"

or to these 2 lines:

[ `expr "${_optLast}" : '/.*'` -eq 0 ] && _optLast="`pwd`/${_optLast}"
_optLast="file://${_optLast}"

obviously, file:// is added to the file name if and ONLY if it has a relative path
file:// is NOT added if the file name has an absolute path

of course, file:// is not added to filenames passed with the -remote switch

this bug is also in Firefox 1.01

Comment 3

[Dirk Jagdmann]

*** Bug 271914 has been marked as a duplicate of this bug. ***

Comment 4

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 5

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.