Closed Bug 223571 Opened 21 years ago Closed 21 years ago

-remote openURL new-tab doesnt broke

Categories

(Firefox :: General, defect)

x86
FreeBSD
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: gerald_davies, Assigned: bugzilla)

Details

User-Agent:       Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031024 Firebird/0.7
Build Identifier: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031024 Firebird/0.7

FreeBSD 4.8, running Firebird 0.7 (port) seems to have a broken -remote command.
When issuing the command and similar combos from the commandline it doesnt seem
to do anything at all.

MozillaFirebird -remote "openURL (bugzilla.mozilla.org, new-tab)" for instance
does absolutely nothing, even though a browser is running.

New-tab doesnt seem to work whereas new-window does.  very odd.  this works fine
on linux, but seems broke on freebsd.  very important feature as i use gaim and
open urls within using the remote command.
 

Reproducible: Always

Steps to Reproduce:
1. install FreeBSD 4.8
2. download mozilla-firebird port
3. launch a browser
4. issue: MozillaFirebird -remote "openURL (bugzilla.mozilla.org, new-tab)"

Actual Results:  
nothing

Expected Results:  
opened a new-tab with the url inside the brackets
It works fine for me if I give it a fully-qualified URL:

./MozillaFirebird/MozillaFirebird -remote
"openURL(http://bugzilla.mozilla.org,new-tab)"

Please re-open if this still doesn't work for you.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031109 Firebird/0.7

I get the exact same problem on FreeBSD 4.9 RC1 using the following command lines:


firebird -remote "openURL(http://www.jobsluder.net,new-tab)"
firebird -remote "openURL(http://bugzilla.mozilla.org,new-tab)"

However

firebird -remote "openURL(http://bugzilla.mozilla.org,new-window)"

works as does

firebird -remote "openURL(http://bugzilla.mozilla.org)"

Perhaps this is a freeBSD build issue?
You need to log in before you can comment on or make changes to this bug.