158436 - Remove collected addresses size limit pref

Status: VERIFIED DUPLICATE of bug 167571

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

Description

[Blake Ross]

I'm trying to cut down on the unwieldy number of prefs we have in our product. 
 Why would a user ever want to limit his collected addresses to 256 or 521 or
913?  Why would there ever be a point at which the user wouldn't want any more
addresses collected?  I think we can safely do away with this pref...Jennifer?

Comment 1

[Blake Ross]

To clarify, I'm referring to the "Limit the..." pref in the Mail & Newsgroups >
Addressing pref panel.

Comment 2

[R.K.Aa.]

uhumm... there is the FIFO principle when it comes to collected addies, so it
doesn't stop at 1000 for instance, it just starts to refresh from there.
People who don't get much mail may want to keep the number low - people who gets
tons might want it at 1000 or more. But no limit at all might just turn out to
make the AB a dreadful performance hit... when there are 90000 collected
addresses etc..

So if the pref is to be removed, it should be replaced by a hidden pref insatead
- and a certain pre-set limit of for instance 1000 collected addresses should be
the default.

Comment 3

[Blake Ross]

Sorry, by

"Why would there ever be a point at which the user wouldn't want any more
addresses collected?"

I meant, why would there ever be such a specific number at which point the user
wants to start collecting new addresses?  Users probably have no concept of how
much 'space' each address takes up on their 'hard drive'.  There is no reason to
believe that any given user would want exactly 491 addresses collected.  We
should decide on a reasonable number and run with it.

Comment 4

[nemo]

Erm.  I learned the hard way.
I set mine large, thinking the same thing.
Ever had to wait 20 seconds just to have an address autocomplete? :)

Comment 5

[(not reading, please use [e-mail] instead)]

taking

Comment 6

[(not reading, please use [e-mail] instead)]

the work for this is in #167571

*** This bug has been marked as a duplicate of 167571 ***

Comment 7

[Vedran Miletic]

v