381696 - numerous regressions in composer addressee pane

Status: VERIFIED DUPLICATE of bug 381553

(MailNews Core :: Composition, defect)

Description

[Nelson Bolyard (seldom reads bugmail)]

Attachment: small screen shot showing problem

Seen in SM 1.5a trunk 20070522 nightly build.  100% reproducible.
Regression since 20070418 build

Mail composer addressee pane (where you put the email addresses of the 
intended recipients) is now all white in the right 60% (more than half)
side.  Affects both html and plain text email composer.

Comment 1

[Nelson Bolyard (seldom reads bugmail)]

In addition to the large white space, it seems that when doing a reply-all
all the addressees are now listed in the addressee pane as To: recipients,
no Cc: recipients.  

If you click on the button that says To: and select Cc:, it doesn't change.
It remains To:

If you click on that button again and select Reply-To: it changes to Reply-To
and the button gets wider.  When that happens the white area gets smaller. 

Once changed to Reply-To:, it can thereafter be successfully changed to Cc:

Comment 2

[Nelson Bolyard (seldom reads bugmail)]

I have one email account setup to Bcc me on all outgoing emails. 
With this new set of regressions, the Bcc address comes up as a To: 
address, not as a Bcc:.  

Sadly, I MUST revert to an older trunk build.  I just can't work with 
this broken email composer. :(

Comment 3

[Tobias Fischer]

Think this was an Duplicate of Bug 381553. Nelson, would you like to check it out? 

Actual Status of the Bug is, that Addresses will be not cut of anymore, but To:-Bar took somethimg like 80% of the Address-Pane. Screenshot from SeaMonkey-Trunk-Build 2007052303 follows. 

Comment 4

[Tobias Fischer]

Attachment: Screenshot from Addressing Newsgroup Reply

Comment 6

[Nelson Bolyard (seldom reads bugmail)]

clearing blocking request for duplicate bug

Comment 7

[Serge Gautherie (:sgautherie)]

(In reply to comment #0)
> {Large blank area}
> Regression since 20070418 build

That's very odd !

As far as I know this regression happened between -0515 and -0516:
that's bug 381553, caused by bug 53901 (on the 15th).
(Myself, I'm still using -0515 and never saw this bug before -0516.)

If you are still seeing this, file a new/separate bug;
otherwise, while a confirmation would be appreciated, I guess it doesn't matter that much anymore.


(In reply to comment #1)
(In reply to comment #2)

These two have now been duplicated/moved to bug 381722.
I'll reply there.


V.Duplicate.