Closed Bug 399213 Opened 14 years ago Closed 3 years ago

location bar autocomplete algorithm should be extensible


(Firefox :: Bookmarks & History, defect)

Not set





(Reporter: dietrich, Unassigned)



[11:38am] dolske: oddball thought -- if we know how long you had a page loaded, we could just that data both for prioritizing the url bar autocomplete and for expiring pages
[11:38am] dolske: [ie, if you visited the page for < 5 seconds, it's probably not of any interest]
[11:40am] dietrich: i'd like to have an autocomplete weighting api
[11:40am] dietrich: for extensions to do stuff like that
[11:42am] gavin|: we could use that weighting API for 370117
Hmm, I was thinking of a generic autocomplete API that lets the nsIAutocompleteController pass "ranking" information back to the nsIAutocompleteSearch implementations (like Places), so my comment about bug 370117 might have been misplaced.
that sounds like an ok approach to me. Places would likely filter post-query anyways.
Blocks: 402991
If I understand this right, this would (potentially) allow the case where there are multiple autocomplete search providers, and the results are wanted to be sorted together (rather than grouped by the provider, like the current system). Taskfox will (eventually) be blocking on having this sort of functionality.
Bug 451915 - move Firefox/Places bugs to Firefox/Bookmarks and History. Remove all bugspam from this move by filtering for the string "places-to-b-and-h".

In Thunderbird 3.0b, you do that as follows:
Tools | Message Filters
Make sure the correct account is selected. Click "New"
Conditions: Body   contains   places-to-b-and-h
Change the action to "Delete Message".
Select "Manually Run" from the dropdown at the top.
Click OK.

Select the filter in the list, make sure "Inbox" is selected at the bottom, and click "Run Now". This should delete all the bugspam. You can then delete the filter.

Component: Places → Bookmarks & History
QA Contact: places → bookmarks
Per policy at If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Closed: 3 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.