Closed Bug 25354 Opened 25 years ago Closed 25 years ago

Address Book back end needs to support some extra columns

Categories

(SeaMonkey :: MailNews: Address Book & Contacts, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: hangas, Assigned: chuang)

Details

The Address Book back end needs to support some extra columns that need to be displayed in the address book results pane. The columns that we need to support are: Name - 1 of 3 options (from prefs): First Last, Last First, or Display Name Nickname Email Additional Email Work Phone Home Phone Fax Pager Cellular Title Department Organization We need Organization for beta1, so it seems like it would be best to just cover them all at once.
Status: NEW → ASSIGNED
Target Milestone: M14
QA Contact: lchiang → esther
M14 and beta1 ok without this. Not sure why we need Organization for B1. M15
Target Milestone: M14 → M15
Fix checked in on 1/31/00.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Using build 2000-03-0-02 on win98, mac and linux I don't see the all the extra columns. We only display Name,Email,Work Phone,Organization in the results pane. The View|Sort only lists these 4. Was the fix to just get "Organization" in, if so I will verify and write up a new bug for the other columns that are missing or reopen this and change Target Milestone to a later milestone noting that Organization is now in.
The fix is just for back end to have all the columns ready so front end can just change the xul file to display what we want to show in the result pane. You need to change abResultsTreeOverlay.xul to add the columns in order to see it. This bug doesn't mean to show all the columns on the front. For other columns need to show in the result pane, maybe we can file a new bug to front end later.
Logged bug 33806 for front-end hookup. Will verify this one and test when 33806 is fixed. If 33806 is fixed and columns don't display I will reopen this one.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.