Offer full-text searching in location bar autocomplete

NEW
Unassigned

Status

Camino Graveyard
Location Bar & Autocomplete
--
enhancement
10 years ago
8 years ago

People

(Reporter: Nick Kreeger, Unassigned)

Tracking

Trunk
All
Mac OS X

Details

(Reporter)

Description

10 years ago
In order to help move away from Mork - we should implement the places code that sits on the 1.9 branch.

With this switch we get:
  * sqlite storage for history / bookmarks  
  * new autocomplete session searching (full text history searching at least)
  * say goodbye to mork!

This is something we should consider and perhaps talk about at the 08 Camino Meet-up.

Comment 1

10 years ago
Yeah, I'm 100% in favour of getting rid of Mork, and getting hooks for full-text history autocomplete would be awesome. (I could have sworn we already had a bug on the latter, but I don't see one.)
Hardware: PC → All
So, this bug as filed is basically a dupe of bug 351351, and rewriting autocomplete is bug 340611.

We can morph this to be about "full text searches in autocomplete" though.
Severity: normal → enhancement
Component: Bookmarks → Location Bar & Autocomplete
QA Contact: bookmarks → location.bar
Summary: Implement places stuff in Camino → Offer full-text searching in location bar autocomplete
Full-text as in page-contents-of-visited-pages, or full-text as in every-word-in-the-history-item-title-or-url?

If it's the latter, Dan's done it; if it's the former, I think we should let Spotlight handle that (like we do bookmark titles and URLs; I have a bug to file on that already).
(In reply to comment #3)
> Full-text as in page-contents-of-visited-pages, or full-text as in
> every-word-in-the-history-item-title-or-url?

Nick, which did you mean?  I think we should dupe this to one of those two, unless you meant something entirely different.

> if it's the former, I think we should let
> Spotlight handle that (like we do bookmark titles and URLs; I have a bug to
> file on that already).

That eventually became bug 537159.
You need to log in before you can comment on or make changes to this bug.