161705 - mozilla -remote "openURL(http://www.google.com, new-tab)" Doesn't Work!

Status: VERIFIED INVALID

(SeaMonkey :: Tabbed Browser, defect)

Description

[Mårten Woxberg]

According to the mozilla.org homepage, new-tab should work since 1.0.1 and
forward. It doesn't..

>mozilla -remote "openURL(http://www.google.com, new-tab)" Doesn't Work!
Should work.. 

Im using version 1.1a.
There should be some EASY TO ACCESS documentation on what parameters I can
send to mozilla so that it's easy to get other programs to open pages
with mozilla. Many programs starts mozilla with the url as an input
but if I have mozilla running already it asks which profile I should use...
I only have one profile and thats me!

Comment 1

[timeless]

1.0.1+ or 1.1+. 1.1a doesn't fit.
1.0.1 doesn't even exist.

Comment 2

[Adrian Ulrich]

bug 149046 and bug 128802 may be interesting for you

Comment 3

[jag (Peter Annema)]

Erh, whatever, timeless. He's using Mozilla 1.1alpha, and it's not his fault
that http://www.mozilla.org/unix/remote.html makes claims about future releases.

The code supporting this was checked in on June 17, with a follow-up fix checked
in on June 19. See bug 116653 for details.

Comment 4

[jag (Peter Annema)]

Reporter: does openURL(http://www.google.com, new-window) work?

Comment 5

[timeless]

from the current page:
openURL (URL, new-tab)
Creates a new tab displaying the specified document. (Will be available in
1.0.1, 1.1 and beyond)

jag: the feature was added in 1.20, in time for
http://bonsai.mozilla.org/cvslog.cgi?file=mozilla/xpfe/components/xremote/src/XRemoteService.cpp&rev=MOZILLA_1_1b_RELEASE
but not in time for 
http://bonsai.mozilla.org/cvslog.cgi?file=mozilla/xpfe/components/xremote/src/XRemoteService.cpp&rev=MOZILLA_1_1a_RELEASE
which was off 1.19.  This bug is invalid.

All the reporter has to do is upgrade to 1.1beta, a nighlty, or a 1.0.1nightly

Comment 6

[jag (Peter Annema)]

timeless: thanks, that's much better than "1.1a doesn't fit".

Comment 7

[sairuh (rarely reading bugmail)]

mass-verification of Invalid bugs.

if you don't think the report is invalid, please check to see if it has already
been reported (it might be a duplicate instead). otherwise, make sure that there
are steps (a valid test case) that clearly display the issue as an unexpected
defect.

mail filter string for bugspam: SequoiadendronGiganteum

Comment 8

[sairuh (rarely reading bugmail)]

email from reporter states that this is no longer a problem for him with moz1.1.