Closed
Bug 479903
Opened 16 years ago
Closed 7 years ago
Need finer control over search; cannot search only Title or URI/L or Tag
Categories
(Firefox :: Bookmarks & History, defect)
Firefox
Bookmarks & History
Tracking
()
RESOLVED
INACTIVE
People
(Reporter: alta88, Unassigned)
Details
currently, no interface exists to search only Title, or to exclude searching the URI/L etc. although one can pass excludeQueries = true as an query option, it's only for the specific case of a place: protocol. in some usages, a URL search may not be desired, and in a custom application, the uri is likely a string leading to misleading results if included in the search.
perhaps option includeItems could be added, with something like
TITLE = 0
TAG = 1
URI = 2
READONLYFOLDER = 4
..
with bitwise summation on the value.
relevant code seems to be here:
http://mxr.mozilla.org/mozilla-central/source/toolkit/components/places/src/nsNavHistory.cpp#6067
Comment 1•16 years ago
|
||
I think the following cover your request.
http://ed.agadak.net/2009/02/firefox-31-location-bar-preferences
http://ed.agadak.net/2008/07/firefox-31-restricts-matches-keywords
Comment 2•16 years ago
|
||
I think this report is looking for this option in the query api
yes, for example when running the search in bookmarks sidebar, there is no lower level way to tune the query, it always loads results into the treeview based on title, tag, and uri match. this is if one is using the Places tree infrastructure rather than urlbar.
Comment 4•16 years ago
|
||
Are you sure you can't already do what you want to do? You should create nsINavHistoryQuery and nsINavHistoryQueryOptions objects, set their attributes as appropriate to your search, convert them to a Place URI using nsINavHistoryService.queriesToQueryString(), and then set your tree view's place attribute to the URI. The tree view's applyFilter() method, which I think you might be using, is a convenience method that's not very powerful. Please see the examples at https://developer.mozilla.org/en/Displaying_Places_information_using_views.
I'd also like to point you to https://developer.mozilla.org/en/Querying_Places, but that doc is pretty underdeveloped right now. A good way to understand the query system is to read over the interfaces:
nsINavHistoryQuery
http://mxr.mozilla.org/mozilla-central/source/toolkit/components/places/public/nsINavHistoryService.idl#733
nsINavHistoryQueryOptions
http://mxr.mozilla.org/mozilla-central/source/toolkit/components/places/public/nsINavHistoryService.idl#869
yes, i've been through the .idl files ;) but since it doesn't seem like there's a keyword that limits to just titles, it didn't seem like the result from queriesToQueryString() would help.
i will try your suggestion and close this bug if the resulting uri can be tuned that way.
iiuc, there is an intent to expose the query uris again; it would be nice if users could have a more powerful query interface just using keywords.
no, there is no way to request a search term to be limited to just a title. i linked above to the source where the code decides..
Comment 7•16 years ago
|
||
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.
Gerv
Component: Places → Bookmarks & History
QA Contact: places → bookmarks
Comment 8•7 years ago
|
||
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•