Closed Bug 77455 Opened 24 years ago Closed 20 years ago

wire up LDAP autocomplete to compose window

Categories

(MailNews Core :: Composition, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: dmosedale, Assigned: srilatha)

References

Details

Attachments

(3 files)

Depends on: 69700, 70933
OK, I've just attached a proof of concept patch which hard-codes in the directory server rather than getting it from prefs. Note that it also hardcodes in the sizeLimit, filterTemplate, and outputFormat, none of which are yet (at the time of this writing) used by nsLDAPAutoCompleteSession. To use this, click on the "Show dependency tree" link, and apply the patches from all the unresolved bugs that the dependency tree points to (there should be 7). Then, apply the patch from this bug (it goes on top of one of hewitt's patches). After rebuilding, LDAP autocomplete should work.
Blocks: 17880
Actually, there's no patch in 69700 itself, so there are only patches from 6 bugs to apply before applying the patch in this one.
QA Contact: esther → yulian
With this you can autocomplete in compose window using the directory server set in the preferences.
Ccing Bhuvan for review
ccing Seth for sr
only one comment: + try { + prefs = Components.classes['@mozilla.org/preferences;1']; + prefs = prefs.getService(); + prefs = prefs.QueryInterface(Components.interfaces.nsIPref); + } + catch (ex) { + dump("failed to get prefs service!\n"); + prefs = null; Don't need to add this code as the global variable prefs is alreay initialized and ready to bu used! If you remove those line, R=ducarroz
please attach a new patch, with ducarroz's suggestions.
ducarroz / srilatha: > document.getElementById('msgRecipient#1').setAttribute("searchSessions", "addrbook ldap") does that mean we only autocomplete on the first addressee only?
No. msgRecipient#1 is just a textbox id
We use the first recipient row, which is the only one declared in xul, as a template for the other one created dynamically. Therefore, yes, it will work...
R=ducarroz
Just checked it in.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla0.9.1
Verified with 2001051604 Wins build.
Status: RESOLVED → VERIFIED
I'm not sure that this is still working, see bug 121415
Reopening as it seems something may have regressed this fix.
Blocks: 121415
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Target Milestone: mozilla0.9.1 → ---
Product: MailNews → Core
Bug 121415 is likely to have not been caused by a regression to this fix -> resolving as fixed again
Status: REOPENED → RESOLVED
Closed: 24 years ago20 years ago
Resolution: --- → FIXED
Verifing the closure. Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9a1) Gecko/20050815 SeaMonkey/1.0a
Status: RESOLVED → VERIFIED
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: