Closed Bug 514825 Opened 16 years ago Closed 15 years ago

Delete and pressing enter on autocomplete result should load the selected item

Categories

(Firefox :: Address Bar, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 470921
Tracking Status
blocking2.0 --- -

People

(Reporter: stream, Unassigned)

Details

(Keywords: ue)

When I want to delete some url from locationbar autocomplete it does not update to the next one, instead it keeps the deleted url in the url bar and when I'm automatically on the next result and press enter, it actually goes to the deleted address. STR: 1. With new profile go to http://www.mozillazine.org/ 2. Go to any link in the same page 3. Go to url bar and enter zine 4. Delete the first entry from mozillazine and press enter Result: The deleted address is loaded Expected: To go on the selected url from the autocomplete
This does not work on search bar too. On input fields the autocomplete works as expected.
Summary: Deleting entry from locationbar autocomplete does not update to the next one → Delete and pressing enter on autocomplete result should load the selected item
Whiteboard: [DUPEME?]
blocking2.0: --- → ?
Looks to be a dupe of Bug 422745 (Bug 467195 also looks to be a dupe)
(In reply to comment #2) > Looks to be a dupe of Bug 422745 (Bug 467195 also looks to be a dupe) Well bug 422745 and 467195 suggests that when deleting something from autocomplete it should be removed from address bar too. In this bug the report is about updating the selected address after something is deleted in the address bar only when you hit enter. Im fine with the current behavior described in bug 422745 because: sometimes I have entered a url which is almost correct but need to correct only one or two letters, in this situation I want to delete the invalid address from the autocomplete but keep that in the address bar so I can correct it and not type everything again.
if it's not a dupe of either of those then it stands on it's own. removing whiteboard.
Whiteboard: [DUPEME?]
This is annoying, but unless this is a regression from Firefox 3.6 (which I'm pretty sure it isn't), this does not block the release of Firefox 4.0
blocking2.0: ? → -
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.