Our old friend is back. I noticed this problem yesterday but thought I just messed things up. But waterson sees it too. If you have to scroll in the envelope of the addressing widget, we lose recipients so your message doesn't get sent to all the people you think it is getting sent to. Jean-Francois, can you make sure this gets to whoever fixed this problem in layout last time. I just read email that nisheeth fixed it last time. He said Hyatt may be working on fixing it this time. Maybe this bug should be assigned to hyatt.
Putting on PDT+ radar.
FYI...here's some history of this bug (2) previous bug numbers: 16709 (which was verified fixed) and 21656 which was opened to include parts that weren't fixed in 16709.
Status: NEW → ASSIGNED
Target Milestone: M13
Here is the easy steps to reproduce the crash: 1) start Messenger 2) Open the account setup (menu edit/Account Setup) 3) Select "Outgoing (SMTP) server" and clear the smtp server name 4) Close the Account Setup by pressing the OK button 5) Create a new message and send it 6) >>> The compose window still there and a error box popup in the front of it 7) Press OK in the Error box 8) >>> CRASH
oops, ignore my last comment, wrong bug!!
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
The problem is gone, hyatt checked it some code related to this this weekend. I can again send message to more that three recipient. However because of another bug (I need to find the number), the select object will not always remenber they current selection, the message will be sent using the recipient type "TO"
Using build 2000012109m13 on win98, 2000012108m13 on linux, 2000012108m13 on mac for a NEW MSG compose only, this is fixed. We don't lose recipients by scrolling the addressing pane to view the 4+ recipients. However, Reply to All does lose all recipients after the 3rd one, and you have to manually add the them back in, but that's another bug (24519). Verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.