Closed Bug 109363 Opened 24 years ago Closed 24 years ago

Chatzilla will not process entered text into fields

Categories

(Other Applications Graveyard :: ChatZilla, defect)

Product:
Other Applications Graveyard
Component:
ChatZilla
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
blocker

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: RobertoDohnert, Assigned: rginda)

References

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:0.9.5+) Gecko/20011030 BuildID: 2001103005 When I type text in chatzilla and press the enter button it will not process the text. It will not let me join a Channel or broadcast anything. I first noticed this bug in the 10 -15 -01 build of Fizzilla and a Previous report has been filed for this bug. But I was unable to locate the bug number Reproducible: Always Steps to Reproduce: 1.Open Chatzilla 2.Join any of the servers 3.Try to join a channel Actual Results: Everything worked upon connect. But it would not enter the text after i typed it Expected Results: Should let me Interact with other chatters upon connect
QA, can we get someone to confirm this, or to see if it also happens on OS9? If it started happening on 10/15, something probably regressed. Didn't ftang land his changes around then?
Frank's TSM code was checked in 10/19 I think. This sounds like some forms control problem possibly. Is it Mac-specific? OSX specific?
I can confirm it on OS X 10.1.1 on a G4/350 running Mozilla BuildID 2001110908. Can't do anything in Chatzilla. I even tried pasting in a carriage return, but that didn't work. Also tried shift-, command-, control-, option- and all combinations thereof with both return and enter. There simply appears to be no way to enter a carriage return, so you can't execute any commands... -rob.
rob, are you assuming a particular key is the return key? the keycode is probably different on mac (return vs. enter).
Status: UNCONFIRMED → NEW
Ever confirmed: true
Mike: I wasn't assuming either key - I tried both the keypad ENTER key and the main keyboard's RETURN key, with all the modifiers. On an inspiration, I did two things (bad, I know, should've tried one at a time). I both trashed my entire Mozilla folder (~/Library/Mozilla) and downloaded a new nightly (20011111506). End result? Chatzilla is now working again ... so I'm not sure if it was a corrupted setting or the new build. I'll keep my eye on it, and see if it occurs again with the current build. Sorry I didn't try the fixes one at a time... -rob.
Update: I just reinstalled the 0.9.5 milestone, and Chatzilla's working fine here, too. -rob.
Rob Griffiths: there are two Rob's on this bug, I think pinkerton was talking to me :) Mike: http://lxr.mozilla.org/mozilla/source/extensions/irc/xul/content/handlers.js#541 I'm assuming 13 is the key I want to watch. This works on Mac OS < 10. Don't mind the e.ctrlKey and the fact that I'm using keyUp handlers, I've migrated to key press and (e.ctrlKey || e.metaKey) on the CHATIZLLA_0_8_5_BRANCH.
This is a dup of 107231. It seems fixed on build 2001111609 (as of this morning).
*** Bug 107231 has been marked as a duplicate of this bug. ***
I removed Moz build 2001111609, in which IRC was working, on Wednsday. After installing .96 on OS X.1.1 Chatzilla was still working. This morning the IRC module stopped sending inputs to the server again. Module: Chatzilla Action: input / commands or text inputs on the command line Expected result: response from the IRC server Results: no response from server
i just saw this with release 096 bits on 10.1.1. something is amiss here.
Pinkerton, can you try installing the chatzilla beta from <http://www.hacksrus.com/~ginda/chatzilla/> ?
another note, this is osx only. works fine on os9
i just tested this. on my osx box (10.1.1), the official 096 bits exhibit this problem. a trunk debug build does not (return/enter work fine). ideas? could it be packaging? could it be tossing an exception because some component isn't there and we just don't see it? nothing shows in the JS Console, but who knows...
Have you tried upgrading to the latest chatzilla beta? The beta uses keypress instead of keyup. How about tracing the execution with Venkman?
i tried the 11/27/01 osx build and it works fine, as does my trunk debug build, but 096 does not. *shrug* doesn't look like bad packaging from what i can tell. whatever it was, it's gone away.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Product: Core → Other Applications
Product: Other Applications → Other Applications Graveyard
You need to log in before you can comment on or make changes to this bug.