Closed
Bug 151223
Opened 23 years ago
Closed 23 years ago
Headers from mail.compose.other.header should not autocomplete addresses
Categories
(MailNews Core :: Composition, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: swaldman, Assigned: vparthas)
Details
(Keywords: polish)
Attachments
(2 files)
1.90 KB,
patch
|
Details | Diff | Splinter Review | |
970 bytes,
patch
|
Details | Diff | Splinter Review |
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc3) Gecko/20020523
BuildID: 2002052309
If a custom header is created using the mail.compose.other.header pref, then Moz
tries to autocomplete it as an email address.
As an example, if a header is created called X-No-Archive:, it's not possible to
simply enter "Yes", as this gets completed to "Yes@mylocaldomain.com".
This behaviour can be avoided by turning off address autocompletion, but that's
rather crippling... Could custom headers possibly have the same status as
Newsgroups:, ie not be considered email addresses? Or better still, make it an
option in the pref.
many thanks
Reproducible: Always
Steps to Reproduce:
1.n/a
Actual Results: n/a
Expected Results: n/a
Comment 1•23 years ago
|
||
good catch. Reassign to varada...
Assignee: ducarroz → varada
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 2•23 years ago
|
||
This patch uses a pref mail.compose.other.autocomplete which I assume needs to
be defaulted in some file somewhere...
Comment 3•23 years ago
|
||
Comment 4•23 years ago
|
||
Looks like someone checked this in as part of another patch.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Updated•20 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•