Various means of searching address disregards the ".position" parameter in user.js



14 years ago
13 years ago


(Reporter: jezza, Unassigned)


1.7 Branch
Windows 2000

Firefox Tracking Flags

(Not tracked)




14 years ago
User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; INTRANETUSER)
Build Identifier: 

When you access the address book, beit via 'Search Addresses' or 'Address Book' 
or otherwise, not every screen defaults to the topmost address book (which is 
controlled by the .position parameter in your user.js/prefs.js file.

Although the list of address books appears correct, some windows will default 
to searching the Personal Address Book. The address book should conform to 
the .position of the address book and search the first one listed.

Reproducible: Always
Steps to Reproduce:
1. Set an address book (perhaps an LDAP one) as your first address book 
(set .position = 1 in your user.js/prefs.js file)
2. From the main mail window, click Window > Address Book
3. Notice your number 1 address book is listed as default.
4. Now go back to the main mail window, and from the Tools menu choose 'Search 
Addresses'. This defaults to Personal Address Book.
Actual Results:  
In some windows, the Personal Address Book is the default and you cannot change 

Expected Results:  
Which ever address book in your config file you have listed as #1 should appear 

Comment 1

14 years ago
A couple of additional notes:

1) I am using Mozilla 1.7.3
2) This is not a duplicate of bug 239109


14 years ago
Version: unspecified → 1.7 Branch


14 years ago
Assignee: sspitzer → mail
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.