Closed Bug 405971 Opened 17 years ago Closed 16 years ago

"New Smart Bookmark..." contextual menu item

Categories

(Firefox :: Bookmarks & History, defect)

defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: faaborg, Unassigned)

References

Details

In areas where we have the "New Bookmark..." contextual menu item (bookmarks toolbar, bookmarks sidebar, library window), I think we should add the item "New Smart Bookmark..." (OS X) and "New Saved Search..." (Windows, Linux), which loads the advanced search UI in the Library window. One open question is if we should leverage external consistency with the native OS file system for our naming (which makes documentation more complex), or choose a cross platform name (which users may not be familiar with).
"One open question is if we should leverage external consistency with the native OS file system for our naming (which makes documentation more complex), or choose a cross platform name (which users may not be familiar with)." I'd say, stick with "saved search". Isn't it pretty illogical to call a (saved search) folder of bookmarks a (singular!) "smart bookmark". Or am I missing something here?
Depends on: 436380
This was a tracking bug for Firefox 3 development, resolving invalid since bug 393510 was resolved as invalid.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
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
You need to log in before you can comment on or make changes to this bug.