Closed
Bug 577681
Opened 16 years ago
Closed 14 years ago
Firefox loads, but the keyboard input is unresponsive for the first 3 minutes
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: davetrader, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.5.4 NET_mmhpset GTB7.1 ( .NET CLR 3.5.30729; .NET4.0C)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.5.4 NET_mmhpset GTB7.1 ( .NET CLR 3.5.30729; .NET4.0C)
Hi
Every time I load Firefox, my home page comes up.
When I try to type, nothing shows up on the screen.
If I wait (approx) 3 minutes, then eventually I can type.
If I type before the 3 minutes, eventually after the 3 minutes or so is up, the words appear from what I typed a few minutes earlier.
Anywhere I try to type. In the input fields of my home page, or on the browser search bar. Just nothing works for 3 minutes.
Can you help??
Reproducible: Always
Steps to Reproduce:
1.Click on Firefox icon on desktop
2.Once Firefox loads to home screen, try to type
3.The keyboard wont work for 3 minutes
Actual Results:
All I do is click on Firefox and once I am at the home screen, I try to type ANYWHERE on the screen and nothing shows up. The cursor just blinks.
Expected Results:
That I can start using Firefox immediately instead of having to wait.
Comment 1•16 years ago
|
||
Well, your UA is messed up, so I would try a new profile. These links can help in diagnosing the issue.
http://support.mozilla.com/kb/Managing+profiles
http://support.mozilla.com/kb/Safe+mode
Version: unspecified → 3.6 Branch
Comment 2•14 years ago
|
||
Considering that the above comment was a solution to the problem (since the reporter hasn't responded in over a year), I'm going to mark this bug as Incomplete.
Reporter, if you can still reproduce this bug in the latest version of Firefox, please reopen this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•