This sounds cool. There have been some discussions about web bookmarking services just having tags and not being able to handle folders (Google bookmarks, del.icio.us, etc.). Tag/label are better than folders in that multiple tags could be assigned to one file, making categorizing more flexible and searching easier compared to folders. On the other hand, folders are more easier to look through with mouse clicking. Tag hierarchy and smart folders could give users the benefit of both tagging and folders. You need to handle sub-tags that are present across multiple parent-tags carefully though. Introducing new syntax for tag hierarchy description may be necessary for this. Using "/" (forward-slash) to indicate the hierarchy of tags may be a good idea. For instance, if tag:foo is under both tag:FOO and tag:BAR, FOO | -foo | -bar BAR | -foo search for "tag:foo" should bring up all bookmarks with tag:foo and search like "tag:FOO/foo" should show all bookmarks with tag:foo that are under tag:FOO When adding bookmark, typing FOO/foo in the tag input field will put the bookmark in the smart folder "foo" under parent smart folder "FOO" but not in smart folder "foo" under smart folder "BAR" .
Confirming as an enhancement request.
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: PC → All
Version: unspecified → Trunk
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
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
Last Resolved: 4 months ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.