[LDAP] Autocomplete email address from LDAP directory [meta]

RESOLVED INVALID

Status

defect
RESOLVED INVALID
20 years ago
7 days ago

People

(Reporter: phil, Unassigned)

Tracking

(Depends on 12 bugs, Blocks 1 bug, {meta})

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: nab-ldap)

(Reporter)

Description

20 years ago
This is a feature tracking bug for autocompleting email addresses in the compose
window using LDAP directories

Updated

20 years ago
Blocks: 10791
QA Contact: lchiang → esther
(Reporter)

Updated

20 years ago
Status: NEW → ASSIGNED
Target Milestone: M15
(Reporter)

Comment 1

19 years ago
P4 per m/n staff mtg today
Priority: P3 → P4

Updated

19 years ago
Target Milestone: M15 → M17

Comment 2

19 years ago
Moving all P4s out of beta2 to M17.

Comment 3

19 years ago
Phil found a way to weasel out of owning this bug.  Reassigning.
Assignee: phil → selmer
Status: ASSIGNED → NEW

Comment 4

19 years ago
[LDAP] in summary
Summary: [FEATURE] Autocomplete email address from LDAP directory → [FEATURE][LDAP] Autocomplete email address from LDAP directory

Comment 5

19 years ago
LDAP to M30, nobody, helpwanted
Assignee: selmer → nobody
Keywords: helpwanted
Target Milestone: M17 → M30

Updated

19 years ago
Blocks: 36557

Comment 6

19 years ago
Changing qa assigned to myself.
QA Contact: esther → pmock
Taking this bug and removing helpwanted.  It would be a really fine thing to
land this for mozilla 0.9.  The exact strategy to take for this has yet to be
hammered out.  In some sense, the more elegant way is to integrate LDAP into the
addressbook first and then let the existing addressbook autocomplete work.  But
realistically speaking, the addressbook is currently tightly wired enough to
Mork and addressbook autocomplete is likely to have dependencies on how long it
may take to return results.  So as a way land this feature sooner rather than
later, my suspicion is that the right thing to do may be to implement
nsI(Ab)AutoCompleteSession ourselves.  The cleanest way would be if it's
possible to run multiple autocomplete sessions on a single textbox
simulataneously.  Not sure whether that's currently possible.  More
investigation to follow; comments invited.
Assignee: nobody → dmose
Keywords: helpwanted
Target Milestone: --- → mozilla0.9

Comment 8

18 years ago
Assign to Hong's group
QA Contact: pmock → hong
Depends on: 70658
Moving to my netscape account.
Assignee: dmose → dmose
No longer depends on: 70658
Status: NEW → ASSIGNED
Depends on: 69700
Depends on: 71247
Depends on: 70933
Target Milestone: mozilla0.9 → mozilla0.9.1
Depends on: 31881
Depends on: 70422
No longer depends on: 70422
Depends on: 77381

Updated

18 years ago
Depends on: 77391

Updated

18 years ago
No longer depends on: 75954, 75989, 75990, 75999, 76782, 76785, 76875, 76887, 77391
No longer depends on: 70422
Depends on: 77452
Depends on: 77455
Depends on: 78232
No longer depends on: 76755
Depends on: 78534
No longer blocks: 77672
Depends on: 77672

Comment 10

18 years ago
setting qa to yulian@netscape.com
QA Contact: hong → yulian
Depends on: 79247

Updated

18 years ago
Depends on: 78926

Updated

18 years ago
Depends on: 79254

Updated

18 years ago
Depends on: 79249

Updated

18 years ago
Depends on: 78979

Updated

18 years ago
Depends on: 79252

Updated

18 years ago
Depends on: 77669

Updated

18 years ago
Depends on: 78993

Updated

18 years ago
Depends on: 76782

Updated

18 years ago
Depends on: 76875

Updated

18 years ago
Depends on: 75990

Updated

18 years ago
Depends on: 75999

Updated

18 years ago
Depends on: 75955

Updated

18 years ago
Depends on: 75966

Updated

18 years ago
Depends on: 76887

Updated

18 years ago
Depends on: 75989

Updated

18 years ago
Depends on: 79488
Depends on: 79509

Updated

18 years ago
Keywords: nsbeta1
Target Milestone: mozilla0.9.1 → mozilla0.9.2
Depends on: 79553

Updated

18 years ago
Depends on: 79756

Updated

18 years ago
Depends on: 79777
Depends on: 79869
No longer depends on: 77384
Depends on: 79885
Depends on: 79792
Depends on: ? 799
No longer depends on: ?
Depends on: ? ?
No longer depends on: ? ?
Depends on: ? ?
No longer depends on: ? ?
Depends on: ? ?
No longer depends on: ? ?

Updated

18 years ago
Depends on: ? ?
No longer depends on: ? ?

Updated

18 years ago
Depends on: ? 78771, 798
No longer depends on: ? 79885, 799
No longer blocks: 80803
Depends on: ? ?
No longer depends on: ? ?
No longer blocks: 80783
Depends on: ? ?
No longer depends on: ? ?

Updated

18 years ago
Depends on: ? ?
No longer depends on: ? ?

Updated

18 years ago
Depends on: ? ?
No longer depends on: ? ?
Depends on: ? ?
No longer depends on: ? ?
Depends on: ? ?
No longer depends on: ? ?
Depends on: ? 79814
No longer depends on: ? 79869
Depends on: ? ?
No longer depends on: ? ?
Depends on: ? ?
No longer depends on: ? ?
Depends on: ? ?
No longer depends on: ? ?
Depends on: ? ?
No longer depends on: ? ?
Depends on: ? 79869
No longer depends on: ? 79509

Updated

18 years ago
Depends on: ? ?
No longer depends on: ? ?

Updated

18 years ago
Depends on: ? ?
No longer depends on: ? ?

Updated

18 years ago
Depends on: ? ?
No longer depends on: ? ?

Updated

18 years ago
Depends on: ? ?
No longer depends on: ? ?

Updated

18 years ago
Depends on: ? ?
No longer depends on: ? ?

Updated

18 years ago
Depends on: ? ?
No longer depends on: ? ?
Untargetting, since this is a meta bug.
Keywords: nsbeta1meta
Target Milestone: mozilla0.9.2 → ---

Updated

18 years ago
Depends on: ? ?
No longer depends on: ? ?
Depends on: ? ?
No longer depends on: ? ?
Depends on: ? ?
No longer depends on: ? ?

Updated

18 years ago
Depends on: ? ?
No longer depends on: ? ?
Depends on: ? ?
No longer depends on: ? ?

Updated

18 years ago
Depends on: ? ?
No longer depends on: ? ?
Depends on: ? ?
No longer depends on: ? ?

Updated

18 years ago
Depends on: ? ?
No longer depends on: ? ?

Updated

18 years ago
Depends on: ? ?
No longer depends on: ? ?

Updated

18 years ago
Depends on: ? ?
No longer depends on: ? ?

Updated

18 years ago
Depends on: ? ?
No longer depends on: ? ?

Updated

18 years ago
Depends on: ? ?
No longer depends on: ? ?

Updated

18 years ago
Depends on: ? ?
No longer depends on: ? ?
Depends on: ? ?
No longer depends on: ? ?
Depends on: ? ?
No longer depends on: ? ?

Updated

18 years ago
Depends on: ? ?
No longer depends on: ? ?
Depends on: ? ?
No longer depends on: ? ?

Updated

18 years ago
Depends on: ? ?
No longer depends on: ? ?
Depends on: ? ?
No longer depends on: ? ?

Updated

18 years ago
Depends on: 92135

Updated

18 years ago
Depends on: 96636
Depends on: 91325
No longer depends on: 75166

Updated

18 years ago
Depends on: 121415

Updated

17 years ago
Depends on: 126022

Updated

17 years ago
No longer depends on: 154017

Updated

17 years ago
Depends on: 100606

Comment 12

16 years ago
Hi there,

Any progress on this, is this available in 1.5.  My entire company's 
addressbook is on the LDAP. We would like to put our clients addresses in the 
LDAP too to share out as a global addressbook but it can't be done because the 
addresses can't be displayed when I click on the LDAP under address book. BTW i 
am using 1.3.  The address would only appear when I key it in in the search 
field.

Comment 13

15 years ago
Hmm.  I'm using moz-mail 1.6 and LDAP auto-complete for mail compose window is
working great!  In the addressbook, LDAP lookup works fine also when you provide
search parameters.

Reading the comments, perhaps this bug should be closed and a new one opened for
auto-loading LDAP entries to the addressbook?

Or, perhaps I don't understand this bug?

Regards,
John
This is a tracking bug.  It exists for purposes of its dependency tree.  Click
the "Show dependency tree" link to see that.
Product: Browser → Seamonkey
Component: Address Book → MailNews: Address Book
Product: Mozilla Application Suite → Core

Comment 15

13 years ago
I know this is implemented (there's an option for this, for Christ's sake), but I'm noticing that it doesn't actually work very well. Or rather it either works fine (sometimes) or just not at all (most times). I've been unable to find out why, up to now. Do I open a bug for this (I couldn't find one) or is this the correct place for this?
Yes, that would be a separate bug.  This is a meta bug used for tracking the dependent bugs.
Assigning bugs that I'm not actively working on back to nobody; use SearchForThis as a search term if you want to delete all related bugmail at once.
Assignee: dmose → nobody
Status: ASSIGNED → NEW
QA Contact: yulian → addressbook
(Assignee)

Updated

11 years ago
Product: Core → MailNews Core
Priority: P4 → --
The remaining dependent bugs seem to be mostly related to performance only.  So, in the sense of "bug", they should not be considered "blocking".  This bug at the current stage seems to be more an enhancement than a bug.  OTOH, some dependent bugs are not really or fully relevant.  To name a few:

Bug 75999: Does the resolution of this bug really have impact on autocomplete?

Bug 80803: This is not only useful for LDAP, but in general situation.

Bug 126022: This is about collected email addresses.  Not autocomplete.

Comment 19

7 years ago
None of the dependent bugs have been updated since 2008 ... can this one be closed?
As this is a tracking bug, it's not correct to close it, well, at least personally, I would vote against closing it.

Updated

5 years ago
Summary: [FEATURE][LDAP] Autocomplete email address from LDAP directory → [FEATURE][LDAP] Autocomplete email address from LDAP directory [meta]

Mostly about ldap XPCOM, and most of this stuff hasn't be touched in 10-20 years. Any further work in ldap is likely be done in new code.

Status: NEW → RESOLVED
Last Resolved: 7 days ago
No longer depends on: 75999, 80803, 126022
Resolution: --- → INVALID
Summary: [FEATURE][LDAP] Autocomplete email address from LDAP directory [meta] → [LDAP] Autocomplete email address from LDAP directory [meta]
You need to log in before you can comment on or make changes to this bug.