Closed Bug 71575 Opened 23 years ago Closed 23 years ago

Opening IRC link in new window causes ghost instance of Mozilla

Categories

(Other Applications :: ChatZilla, defect)

x86
Windows 98
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: Junk_HbJ, Assigned: rginda)

References

()

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; 0.8.1) Gecko/20010309
BuildID:    2001030904



Reproducible: Always
Steps to Reproduce:
1. Load page http://www.mozillazine.org/build_comments/
2. Right-click on one of the "here" links to join mozillazine chat
3. Choose "Open Link in new window" from the context menu

Actual Results:  Chatzilla not startet, but new browser window opened.
In "Tasks" appears a nameless entry, staying in memory even after all Mozilla
windows were closed.

Expected Results:  Chatzilla being launched.

I've twice reinstalled my build, cleaned old user data and even created a new
profile, so (at least I hope so:-\ ) my box isn't to blame.

The point of the bug is that a "ghost" instance of Mozilla is created (visible
in "Tasks") which even remains after *all* Mozilla windows are closed. This
little "ghost" can only be killed with Ctrl-Alt-Del.
This is definately happening on win2000 with a build from march 9
confirming
Status: UNCONFIRMED → NEW
Ever confirmed: true
Could you try opening up components/chatzilla-service.js in your mozilla
directory, and changing the line

        w.open("chrome://chatzilla/content/chatzilla.xul?" +
               channel.URI.spec,
               "_blank", "chrome,menubar,toolbar,resizable");

into...

        w.openDialog("chrome://chatzilla/content/chatzilla.xul?" +
                     channel.URI.spec,
                     "_blank", "chrome,menubar,toolbar,resizable");

Status: NEW → ASSIGNED
Upper patch fixes the problem for me.
Depends on: 71468
superbug checked in, mass marking all dependents fixed.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Product: Core → Other Applications
Status: RESOLVED → VERIFIED
Keywords: verifyme
You need to log in before you can comment on or make changes to this bug.