349549 - -remote 'openURL(URL,new-tab)' fails: "509 internal error"

Status: RESOLVED WORKSFORME

(SeaMonkey :: General, defect)

Description

[Miguel Julier]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.8.0.6) Gecko/20060730 SeaMonkey/1.0.4
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.8.0.6) Gecko/20060730 SeaMonkey/1.0.4

I used to do a "remote" call to open an URL in a new tab of an existing navigator.

It used to work perfectly with Mozilla 1.7
With SeaMonkey it fails.

$ seamonkey -remote 'openURL(google.fr,new-tab)'
Error: Failed to send command: 509 internal error

However, 'openURL(google.fr)' and 'openURL(google.fr,new-window)' still work normally.


Reproducible: Always

Steps to Reproduce:
1. seamonkey &
2. seamonkey -remote 'openURL(google.fr,new-tab)'


Actual Results:  
Error: Failed to send command: 509 internal error

The application itself goes on without any change (does not hang, but no tab is opened, and the URL is not opened)

Expected Results:  
In the existing navigator window, a new tab should show up, with the designated URL. It used to raise the window and to select the new tab (this was nice).

Comment 1

[WADA:World Anti-bad-Duping Agency]

(In reply to comment #0)
See Bug 308076 Comment #19 and Bug 308076 Comment #26.
This is probably a result of intentional change by Bug 289383, and SeaMonkey is also affected, since Product/Component of Bug 289383 is Core/X-Remote.
(Please note that Bug 308076 was already closed as WONTFIX on 2006-05-24)

Comment 2

[WADA:World Anti-bad-Duping Agency]

Killing of -remote on Linux was done by Bug 280725 (Toolkit/XRE Startup).
Sorry for mistake and spam.

Comment 3

[Misak Khachatryan]

confirming bug on both 1.1.9 and Mozilla/5.0 (X11; U; Linux i686; rv:1.9b5pre) Gecko/2008032501 SeaMonkey/2.0a1pre. 

Comment 4

[Andrew Schultz]

google.fr isn't a URL, it's a hostname.  if you use http://google.fr/ it will work.  trunk (SM 2.0) already has this fixed and (at this point), SM 1.1 is unlikely to get fixed.

With 1.1, you can just use the seamonkey start script when a seamonkey process is already running

seamonkey google.fr

works

anyway, resolving WFM on trunk