Closed
Bug 27085
Opened 25 years ago
Closed 25 years ago
Scrolling in Addressing Widget resets send option to "To"
Categories
(SeaMonkey :: MailNews: Message Display, defect, P3)
Tracking
(Not tracked)
People
(Reporter: sol, Assigned: bugzilla)
Details
(Whiteboard: [PDT+])
If you enter 5 names in the addressing widget, set the send option for all but
the first name to "cc", then scroll up and down in the addressing widget, all of
the send options will be reset to "to". If you then send the message, the send
option for each recipient has been reset to "to". In other words, this is not
just a display problem in the addressing widget, but rather a resetting of the
send option.
Build ID: 2000-02-08-17 (mozilla)
Steps to reproduce:
1. Launch Mail
2. Compose a mail message. Include 5 recipients in the addressing widget
3. Set all but the first recipient to receive the message as a "cc"
4. Scroll up and down in the widget
Note: The "cc" option you specified in step 3 has now been reset to "to"
5. Send the message
Expected result - recipient #1 receives the message as "to", recipients #2
through 5 receive the message as "cc"
Actual result - recipients #1 through 5 receive the message as "to"
Nominating for Beta1. This bug has a high frequency of occurence, and results in
data loss which causes the sender to have little confidence that his/her mail
will be sent as intended - thereby leading to limited use of the product.
Keywords: beta1
Comment 2•25 years ago
|
||
I thought we had this bug before, but that it was fixed. JF, can you look into
it?
Assignee: phil → ducarroz
Assignee | ||
Comment 4•25 years ago
|
||
Rods, Does it has been already fixed?
I cannot test yet because my Windows build isn't done and because Mac/Unix will hang because of bug 26618.
Status: NEW → ASSIGNED
Assignee | ||
Comment 5•25 years ago
|
||
*** This bug has been marked as a duplicate of 21945 ***
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•