Closed
Bug 250406
Opened 20 years ago
Closed 20 years ago
Some context menu options greyed out
Categories
(Other Applications :: ChatZilla, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: thib+mozilla, Assigned: rginda)
References
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1 [INFO] Chatzilla 0.9.64d [Mozilla rv:1.7/20040626] On Undernet, DALnet and Freenode, I am experiencing a situation where the 'Whois', 'Open Private Chat' and 'Get Version Information' commands are greyed out in the context menu after a right click on a user's name or message in the main panel (but everything works as expected in the user list panel). However, upon logging on to Moznet's #chatzilla, I noticed that things worked normally. Reproducible: Always Steps to Reproduce: This is what I do: 1. Log on to a channel on Undernet, Freenode or DALnet (possibly others...) 2. Wait till someone says something. 3. Right-click the user's name, or the user's message, in the main panel. 4. Right-click the user's name in the user list panel. Actual Results: 3: Some options are greyed out, such as 'Whois'. 4: The options are available, such as 'Whois'. Expected Results: 3: The options should have been available for me to click. Note that when I logged on to Moznet to talk about this issue, things worked as expected (Murphy's Law) on Moznet. I was directed to perform the following test: /eval dd = function (msg) { client.displayHere(msg) } /pref debugMode c Then I right-clicked on a user (fee) in the main panel on Undernet. I got the following message in the client tab: [INFO] context 'context:messages' + originalEvent (object) + sourceObject (object) + TYPE (string) 'IRCChannel' + parent (object) + user (object) + channel (object) + server (object) + network (object) + viewType (string) 'Channel' + channelName (string) '#grenoble' + networkName (string) 'undernet' + url (string) 'irc://irc.undernet.org/fee,isnick' + nickname (string) 'fee' + canonNick (string) 'fee' + menuManager (object) + contextSource (string) 'context:messages' * Any subsequent right-click on user fee produced the right results (no greying out). But any right-click on other users past that first one produced greying out and result in the client tab as follows: [INFO] context 'context:messages' + originalEvent (object) + sourceObject (object) + TYPE (string) 'IRCChannel' + parent (object) + user (object) null + channel (object) + server (object) + network (object) + viewType (string) 'Channel' + channelName (string) '#grenoble' + networkName (string) 'undernet' + url (string) 'irc://irc.undernet.org/bzzbzz,isnick' + menuManager (object) + contextSource (string) 'context:messages' * Further weirdness: After talking about this on Moznet's #chatzilla, I closed and re-opened ChatZilla to make a clean fresh test so that I could post it here. I only logged on to Undernet this time, *not* Moznet, and performed the above test, and it failed every time, for everyone, including the first user clicked. But then I just said: /attach moznet and miraculously the first right-click I made worked and produced the results above!
Assignee | ||
Comment 1•20 years ago
|
||
in the second context object, the user object is null, but the url is correct... strange.
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040629 Firefox/0.9.1 [INFO] Chatzilla 0.9.64d [Mozilla rv:1.7/20040629] It's even more confusing there. I tried out several places on Undernet, Freenode and DALnet and sometimes the commands are greyed out, sometimes not. (Mostly greyed out.)
Comment 3•20 years ago
|
||
The key is subtle. It's the nickname of the user you're right-clicking - if their nickname isn't all lower-case, it fails. I have it fixed here for 0.9.64e.
(In reply to comment #3) > The key is subtle. It's the nickname of the user you're right-clicking - if > their nickname isn't all lower-case, it fails. I have it fixed here for 0.9.64e. Good job :-)
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Product: Core → Other Applications
You need to log in
before you can comment on or make changes to this bug.
Description
•