Closed Bug 385712 Opened 17 years ago Closed 6 years ago

Places Tree View should allow custom columns

Categories

(Firefox :: Bookmarks & History, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED INACTIVE

People

(Reporter: wesj, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a6pre) Gecko/20070624 Minefield/3.0a6pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a6pre) Gecko/20070624 Minefield/3.0a6pre Adding a custom column to the places treeview involves either writing a new treeview, or overwriting methods within the current one (which won't work if multiple extensions are adding multiple columns). Mailnews's msgDBView has methods (AddColumnHandler and RemoveColumnHandler) to make that easier. Places should allow something similar. Here's a link to the mail code for reference: http://mxr.mozilla.org/mozilla/source/mailnews/base/src/nsMsgDBView.cpp Reproducible: Always Steps to Reproduce: 1. 2. 3.
Blocks: 402231
Priority: -- → P3
Target Milestone: --- → Firefox 3.1
Status: UNCONFIRMED → NEW
Ever confirmed: true
Blocks: 437247
Target Milestone: Firefox 3.1 → ---
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
Priority: P3 → --
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: 6 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.