Closed Bug 462710 Opened 12 years ago Closed 2 years ago
improve tag browsing and managing
some comments starting here: https://bugzilla.mozilla.org/show_bug.cgi?id=415960#c64 A first stab at a better tag browsing UI in the Library is here: http://autonome.wordpress.com/2008/07/09/better-tag-browsing/
Dietrich, this looks like a hierarchical list for tags or where do you get the information that vegan is under food?
Component: Bookmarks & History → Places
QA Contact: bookmarks → places
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
Thanks for pointing this out! Agree that the tags and bookmarks have much space to improve. Tag is probably a feature that very few people use. The current interface does not really help promote the value of using tags. I believe if we plan to improve tags, there is more work needs to be done besides just improving the visual hierarchies. Delete uiwanted for now. It's currently not on the priority list for UX. But we will keep us thoughts on the bookmarks and tags feature for sure.
"Tag is probably a feature that very few people use. The current interface does not really help promote the value of using tags" i think bad interface result in rare use. would you like to check a delicious bookmarks addon interface, i think it's very nice and clear, but this extension seems to be dead.
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: 2 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.