If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Launching link from xchat to existing mozilla window doesn't work

RESOLVED FIXED

Status

SeaMonkey
General
RESOLVED FIXED
17 years ago
13 years ago

People

(Reporter: Yusuf Goolamabbas, Assigned: asa)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

17 years ago
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.19 i686; en-US; rv:0.9+) Gecko/20010522
BuildID:    2001052213

Hi, I am using XChat 1.4.3 on a Redhat 7.0/Ximian 1.0 box
I used to be able to click on URL's inside Xchat and launch them in existing
Mozilla windows.

I can't seem to do this with Build 2001052213. I can only launch via a new
window. I don't see this behaviour with Mozilla 0.9 or Netscape 4.76


Reproducible: Always
Steps to Reproduce:
1.Launch Xchat, go into a channel
2. Type a URL http://www.mozilla.org
3. Take your mouse and hover over the URL, right click. You'll get a menu. Click
on Netscape (existing). 
4. also, try clicking on Netscape (new Window)

Actual Results:  Clicking on Netscape (existing) does nothing
Clicking on Netscape (new Window) launches a new window with the URL loaded


Expected Results:  Clicking on Netscape (existing) must switch existing page to
the URL in XChat

Comment 1

17 years ago
See also bug 75138 which would make this a "pref". The current behavior should
stay as a default.

Comment 2

17 years ago
related to bug 77160? (gnome integration)

Comment 3

17 years ago
This is very probably related to bug 41527 / bug 83092. If you check the xchat
options, it is most likely using mozilla -remote to open the URL

Comment 4

17 years ago
Created attachment 36800 [details]
Gif of xchat URL handlers

Comment 5

17 years ago
If you look at the attached gif, you can see the handlers for Netscape. The
mozilla one I added myself based on the NS ones. This clearly demonstrates a
dependancy on 'mozilla -remote' working.

Comment 6

17 years ago
Reporter, can you please retest this now that bug 41527 has been fixed.
(Reporter)

Comment 7

17 years ago
Works now with build 2001060521, marking this bug as resolved
Thanks to all
Status: UNCONFIRMED → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → FIXED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.