Add preferences option for how addresses should display

RESOLVED EXPIRED

Status

--
enhancement
RESOLVED EXPIRED
17 years ago
9 years ago

People

(Reporter: hakon_, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

17 years ago
I want the "zip code" to be displayed *before* the "City", and no comma inbetween.
Rather that making full I18N support, which would be quite complicated, why not
let the user somehow define how the address should be displayed.
E.g. >display address as: "&z &c" or "&c, &z"<
To addressbook.
Assignee: nhotta → racham
Status: UNCONFIRMED → NEW
Component: Internationalization → Address Book
Ever confirmed: true
QA Contact: ji → nbaca

Updated

17 years ago
Status: NEW → ASSIGNED
Target Milestone: --- → Future
mass re-assign.
Assignee: racham → sspitzer
Status: ASSIGNED → NEW

Comment 3

16 years ago
I would like address's to be displayed in the main view then all one has to do
is click on the name displayed to send messages.That ok???? Thanx

Comment 4

15 years ago
hello -- is this bug id appropriate for "provide end-user customization of 'edit
address' book fields -- and subsequent layout??"  -GA
Product: Browser → Seamonkey

Updated

14 years ago
Assignee: sspitzer → mail
QA Contact: nbaca → addressbook
Target Milestone: Future → ---

Comment 5

10 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED

Comment 6

9 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.