Closed
Bug 375953
Opened 18 years ago
Closed 18 years ago
Previous autocomplete entries are set to erase typed text merely by moving your mouse over it
Categories
(Firefox :: Tabbed Browser, defect)
Tracking
()
People
(Reporter: ultrafire7, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
Type something you commonly type in a search engine like google but type something different which you've never typed before. Autocomplete will bring up a list of previous entries. Move your mouse down over the these entries (a typical movement people make I'm sure) and press enter. The typed text will revert back to the saved entry that was last highlight by the mouseover and will search using the old entry. Grrr.
Reproducible: Sometimes
Steps to Reproduce:
1. Type something you commonly type in a search engine like google but type something different which you've never typed before. Autocomplete will bring up a list of previous entries.
2. Move your mouse down over the these entries (a typical movement people make I'm sure).
3. Press enter; the typed text will revert back to the saved entry that was last highlight by the mouseover and will search using the old entry. Grrr.
Actual Results:
Wrong information is searched for.
Expected Results:
For the information I wanted to be searched for to be searched for.
Why does this stupid bug remain? It should not show the previous entries once the data entered is different from all previous entries as a quick fix. IE does not have this stupid bug.
This bug may be a duplicate of 357220 but I am unsure because whoever entered it didn't use the best wording or grammar, at least that's my opinion.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
Updated•18 years ago
|
Status: VERIFIED → RESOLVED
Closed: 18 years ago → 18 years ago
Resolution: WONTFIX → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•