Closed Bug 798765 Opened 12 years ago Closed 12 years ago

Cannot delete inline autocomplete result in address bar

Categories

(Firefox :: Address Bar, enhancement)

15 Branch
x86_64
Windows 7
enhancement
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: alexhaan, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20100101 Firefox/15.0.1 Build ID: 20120905151427 Steps to reproduce: I know this (the summary) sounds very similar to https://bugzilla.mozilla.org/show_bug.cgi?id=726835. But I have different expectations. I once typed "awesomesite" in the address bar. The inline autocomplete now has that remembered. I only visited that site once though and I don't care to visit it again. Similar to the Awesomebar results, I want to be able to simple delete (shift+delete there) a result I never want to see again. Bug 726835 mentions clearing the history. But I have the offending entry right there. I don't want to have to jump through hoops to remove that result. It should be nearly as easy to remove an unwanted result as having one added (which is as simple as once typing a url, of course deletion can never be that simple, but it should be close). Actual results: The unwanted result keeps showing. Expected results: The unwanted result should never show again.
Component: Untriaged → Location Bar
Severity: normal → enhancement
As a currently usable solution, you can open history sidebar, set it "by site", then right click on the offending domain and "Forget about this site". While would be cool to be able to delete entries from inline completion, I suspect it would badly interact with the text field (if you press backspace or delete you likely expect it to act on the text you are editing).
not an easy task to figure a way to remove something that is filled as a new selection... I think we'll have to continue relying on common history removals methods for now.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.