Closed Bug 180518 Opened 22 years ago Closed 21 years ago

Context menu in ChatZilla appears to be corrupted.

Categories

(Other Applications :: ChatZilla, defect)

x86
Windows 2000
defect
Not set
trivial

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: deven, Assigned: rginda)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021016
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021016

ChatZilla seems to be broken in 1.2beta.

IRC links no longer work in the browser; they return an "irc is not a registered
protocol" error.  (This used to work in previous versions of Mozilla.) 
ChatZilla can still be launched from the menu or toolbar, but the links in the
*client* tab don't work anymore either (no response at all).  The context menu
from right-clicking on those links also appears to be corrupted.

Attempting to connect to a server with a command like "/server irc.mozilla.org"
does open a new tab for the server, with the message "Connecting to
irc.mozilla.org via irc.mozilla.org:6667, attempt 1 of 5...", but it simply
hangs at this point.  It never connects, nor does it make additional attempts.

Meanwhile, "telnet irc.mozilla.org 6667" connects to the IRC server without
trouble, so it's not a network connectivity problem.

Reproducible: Always

Steps to Reproduce:
1. Enter "irc://irc.mozilla.org" into browser location bar.
2. Launch ChatZilla via "IRC Chat" in Window menu.
3. Click on one of the links in the *client* tab, such as "moznet".
4. Try right-clicking on the same link.
5. Type "/server irc.mozilla.org" in the ChatZilla window.

Actual Results:  
From the browser, it generates the "irc is not a registered protocol" error.

From the ChatZilla window, links don't work, and the context menu has 4 blank
entries at the start, and a blank entry with a (duplicated) shortcut at the end.

The "/server irc.mozilla.org" command creates a new tab for the server, but does
not successfully connect to the IRC server, although the computer CAN connect to
the same IRC server via the "telnet" command.

Expected Results:  
All of these attempts should have been able to successfully connect to an IRC
server to start chatting.  This is a regression; these things used to work fine.
Marking as a blocker for bug 179176, as this is a regression and breaks a major
Mozilla component.
Blocks: 179176
Worksforme with linux trunk build 20021116 and 1.2b
do you see this with a clean profile?

this has *nothing* to do with bug 179176 (bugzilla not chatzilla)
No longer blocks: 179176
Whoops, sorry.  Misread bug 179176 as being a bug for Mozilla regressions;
didn't catch that it was for the Bugzilla software itself.  My bad!

I don't know if this bug is Windows-specific, but I'll test it with a clean
profile just to be sure it's consistent.  (Of course, if it is a problem with
the profile, that's still a bug, since upgrades after 1.0 have no excuse to
break on an old profile!)

I'll report back after testing with a new profile.
Just to make sure it wasn't a problem in Windows itself, I rebooted and tried
again with my normal profile -- no change in behavior.

I then exited Mozilla and launched it through the Profile Manager.  Created a
new profile, which launched the browser with the classic interface (I use
Modern) -- again, no change.  I still get the "irc is not a registered protocol"
error, the links in the *client* tab still don't work, and "/server
irc.mozilla.org" still can't connect even though telnet can.  The only
difference is that it asked me for a nick when I typed the "/server" command,
since it didn't have one already stored in the profile.

If this is WORKSFORME under Linux, could someone else test it under Windows with
the 1.2beta that's linked for download on the mozilla.org front page?  (This is
Windows 2000 Professional; if it works for someone else under Windows, please
note which version of Windows it worked with.)

I guess I'll try downloading the latest nightly and see if it's fixed there...
I just downloaded build 2002111512, and it seems to be fixed, except for the
problems with the context menu in the *client* tab.  The irc: links work again,
and the links in the *client* tab work again, and it can connect to an IRC
server again.  Since there's still a problem with the context menus, I won't
close this bug outright, but I'll morph it to represent the remaining problem,
and drop the severity to minor...

It's not only the context menus on the links in the *client* tab that look
wrong, but also the context menus on nicks in the chat tabs.  (In the text pane,
not the sidebar list.)  There are 4 empty entries in the menu (all 4 together
are about the height of a normal menu entry), followed by a separator.

[...]

Okay, this may be difficult to reproduce.  I just checked again, and in the same
ChatZilla window that earlier had the corrupted menus, the context menus look
fine.  It may only happen immediately after starting ChatZilla, I don't know.

If nobody else can reproduce this, it might as well be closed as WORKSFORME, but
because it spontaneously fixed itself, I'm dropping the severity all the way
down to trivial instead.
Severity: major → trivial
Summary: ChatZilla broken: "irc is not a registered protocol" → Context menu in ChatZilla appears to be corrupted.
fixed
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Product: Core → Other Applications
You need to log in before you can comment on or make changes to this bug.