Closed
Bug 213025
Opened 22 years ago
Closed 22 years ago
Return key not working
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
People
(Reporter: tvandyke, Unassigned)
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:1.2.1) Gecko/20021130
When I first installed Mozilla about 5 months ago, everything was working fine.
I have stopped using mozilla (about 1 month ago) because it is very difficult
to get to a web page if (problem/bug being stated here) the RETURN key (& ENTER
key) is not functionable anymore.
I have tried re-downloading, installing the most current version, deleting the
preferences, entering a new profile; but still nothing works.
the only way I can get to a web page, is to type in the address, hit the Search
button and then click on the link the search program gives me.
(very time comsuming)
Can't / Won't use Mozilla until bug is solved :(
The RETURN key works with all other programs/applications on my computer (MS
Word, Netscape, MS Internet explorer, Opera 6.0) so it can not be the computer
or the keyboard cable.
Why did it work for a few months then suddenly stop working?
Reproducible: Always
Steps to Reproduce:
1. Start program
2. type wed page in address field
3. Hit return/enter to get to the web page,.... Nothing happens
Actual Results:
Nothing happens, that is the problem.
Expected Results:
fix bug or install a 'Enter' button to click on
Mac G3
dual 867 mhz
768 MB memory
OS 9-Classic
(tried OS X-too confusing, switched back to OS 9)
Mozilla 1.2.1
Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:1.2.1) Gecko/20021130
Comment 1•22 years ago
|
||
For a possible fix read the release notes :
http://www.mozilla.org/releases/mozilla1.2.1/
(section NAVIGATOR or search for "return" in the document)
*** This bug has been marked as a duplicate of 90337 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•