Closed Bug 96234 Opened 23 years ago Closed 23 years ago

address autocomplete broken

Categories

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

PowerPC
Mac System 9.x
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: tracy, Assigned: chuang)

Details

seen on Mac commercial build 2001-08-21-04-trunk

-open mail
-open a new message
-begin typing addressee

expected behavior:  the autocomplete function should be showing possible 
complete addressees

tested behavior: autocomplete is not working at all.
Hardware: PC → Macintosh
Change component to Address Book.
Assignee: mscott → chuang
Component: Networking - General → Address Book
QA Contact: huang → fenella
is it auto complete that's failing or is it not finding matches in your
collected address book. If it's the later then this is a dup of: 96809.
Scott, you meant bug 96089. Right?
I'm note sure of the difference between the two.  All I can tell is that it is 
not working.
this is working as of mac commercial build 2001-08-22-04-trunk

marking wfm
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
seeing this again... it is happening on classic skin only... 

reopening
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
mac commercial build 2001-08-27-04 in classic skin now seems to be working fine 
for me.  hmmmmm...did anybody else see this bug. Perhaps it was just local to my 
machine/profile?
okay it's not my machine only.  I just saw this on another machine on OS X in 
classic skin.
QA Contact: fenella → nbaca
i believe this may be a dupe of bug 97141
20010904 MacOS builds

LDAP autocomplete did fail on both MacOS 9.x and OS X in classic skin sometimes.
Not always reproducible.
20010910 0.9.4 branch build

Working on both MacOS 9.2 and MacOS X on classic skin.

marking mfm as seen on mac build 2001-09-11-03-0.9.4
Status: REOPENED → RESOLVED
Closed: 23 years ago23 years ago
Resolution: --- → WORKSFORME
Verified Worksforme.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.