Closed Bug 229880 Opened 21 years ago Closed 19 years ago

Cannot modify addressing in draft if malformed address exists

Categories

(MailNews Core :: Composition, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: droberts29, Assigned: sspitzer)

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031208 If a message containing a malformed address is saved as a draft then closed and reopened from the draft folder, the message addressing can not be modified. This is problematic in some situations where the user generates an address list outside of Netscape and pastes it into place. This could also indicate a more serious internal processing issue. Reproducible: Always Steps to Reproduce: 1. Compose a new message. Use the following addressing: To: "addr1" <addr1@nowhere.test> Cc: "addr2" <addr2@nowhere.test>, "addr3" <>, "addr4" <addr4@nowhere.test> 2. Save the message as a draft and close the composition window 3. Browse to the Drafts folder and double click on the draft message Actual Results: Observe that the address fields remain greyed out indefinitely Expected Results: Either: 1) Produced an error message when the malformed email address was entered in the first place, or 2) Populated the address fields as usual, including the malformed address This is an issue in Netscape 7.1, Mozilla 1.5 and Mozilla 1.6b
Product: MailNews → Core
Also visible in Thunderbird 1.0.
Status: UNCONFIRMED → NEW
Ever confirmed: true
I don't know what's been done to fix this, but it's working much more nicely with TB 1.5; all the addressing fields are filled and operating, except the one corresponding to the illegal address, which is simply blank. Dan Roberts, can you verify with a Moz 1.8 or Seamonkey 1.0 build? If so, please mark this bug: Resolved | WorksForMe
No response from reporter; => WFM
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.