Closed Bug 365233 Opened 18 years ago Closed 16 years ago

no keyboard response in address window or othe text fields

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: mfelberbaum, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1 On some web pages (random) the keyboard fails to work when you try to type in the address bar or text fields. I have to leave Firefox type something elsewhere before it works again. Reproducible: Sometimes Steps to Reproduce: 1. 2. 3.
I've had this happen to me too (OS X 10.4, though I don't use Firefox enough on other platforms to say whether or not it happens on them). I wonder if bug 216288 is at all related--it's about loss of keyboard AND mouse functionality in Linux, though the latest commenter did say he only experienced keyboard loss...
This happens to me all the time. I will be surfing, and then randomly the no keyboard strokes will work in Firefox 2.0.0.1 Usually the way to stop it is to minimize and then open a new program, type in that program, and then maximize Firefox and keyboard will be responsive. However, yesterday it got to the point where I had to log off my user, and then when I tied to type in my password, only select keys were functioning, so I had to shut down and restart before it started working properly. I called Apple and asked them foe help, followed their steps, but it happened to me again just now. I am using Max OS 10.4.8 On a Powerbook G4 15" This never happened in the original version of Firefox. I cannot figure out how to reproduce the bug, since it happens randomly and without any provocation that I can discern.
As I noted in bug 368896, I'm seeing something similar in trunk builds. However I can't reproduce this the same way on Firefox 2 builds (using the method given in bug 368896 comment 4), so it's possibly an entirely different bug with similar symptoms. I wonder if your (Firefox 2) bug is due to bug 355071 (which is due to Flash)...
The trunk bug is filed as bug 383579.
do you still see this bug in FF2, or bug 345591 or bug 383579 in FF3?
I don't remember having seen this bug lately (Firefox 3.0 final on OS X), or at least not with such frequency as there was a couple years ago--I can't remember the last time I had this problem.
=> WFM per comment 7. Thanks.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.