Closed
Bug 125821
Opened 23 years ago
Closed 16 years ago
code cleanup of LDAP autocomplete pref panel js, addressbook properties js
Categories
(SeaMonkey :: MailNews: Address Book & Contacts, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 305434
People
(Reporter: sspitzer, Unassigned)
References
Details
code cleanup of LDAP autocomplete pref js there is some autocomplete pref js that is doing stuff that the back end code already does. spefically, we have js to enumerate all ldap servers, for dynamically determining the unique "prefname", for poking the prefs when adding or deleting or modifying ldap servers. instead, we should be using the existing nsIAddressBook interface, to which we need to add a modify() some bugs that relate to this: 124057 nor -- PC srilatha@netscape.com NEW mozilla0.9.9 nab-ldap when I delete addressbooks from the prefs (addressing panel) 124059 nor -- PC srilatha@netscape.com NEW --- nab-ldap when I add LDAP directories from the prefs (addressing panel 124061 nor -- PC srilatha@netscape.com NEW --- nab-ldap when I delete a LDAP directory from the addressbook, there a 124064 nor -- PC srilatha@netscape.com NEW --- nab-ldap when I add an LDAP directory from the addressbook (not imple 124553 nor -- PC srilatha@netscape.com NEW --- nab-ldap Changes to LDAP properties in Address Book window not reflec
Reporter | ||
Comment 1•23 years ago
|
||
one more bug, #125823 (add modify() to nsIAddressBook.idl and use it.) there's a lot of code to clean up, we shouldn't be writing or reading from prefs directly. I don't think we need to re-write all the code before 0.9.9 or 1.0, but we should start with the code that writes prefs, and later fix the does the reading. the reason we need to fix the write-pref code first, is that it poking prefs directly causes bugs that the user can see.
Updated•22 years ago
|
QA Contact: nbaca → gchan
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•16 years ago
|
Assignee: cavin → mail
QA Contact: grylchan → addressbook
Comment 4•16 years ago
|
||
The remaining work on this will be done in bug 305434.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•