If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

To: line in message pane broken

VERIFIED DUPLICATE of bug 27242

Status

SeaMonkey
MailNews: Message Display
P3
normal
VERIFIED DUPLICATE of bug 27242
18 years ago
13 years ago

People

(Reporter: Richard Zach, Assigned: Phil Peterson)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

18 years ago
The to: line in the message pane refuses to display the addressees of the
message being displayed.  It's ok for the first message displayed, but broken
for subsequent messages.  Collapsing the To: pane and expanding again solves the
problem.

To reproduce:
1. Open message folder
2. Select message
3. Select another message

Actual result:
The To: line is blank

Expected result:
The To: header lines of the message should be displayed.

Linux build 2000.02.02.09
(Assignee)

Comment 1

18 years ago

*** This bug has been marked as a duplicate of 25048 ***
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → DUPLICATE
(Reporter)

Comment 2

18 years ago
Hmm, I got a permission denied error for bug 25048.  Wrong bug?  Or are
classified security issues manifesting themselves so innocuously?  Anyway,
someone else will have to verify this.

Comment 3

18 years ago
I'll mark as verified duplicate.
Status: RESOLVED → VERIFIED

Comment 4

18 years ago
I can only reproduce this sometimes, when I interrupt the display by selecting
another msg during rendering of the msg before. Letting some more messages
render completely (i.e. clicking slowly) fixes the problem again.

Why should a bug, that manifests itself in Mozilla, being hidden? This seems
wrong to me.
(Assignee)

Comment 5

18 years ago
It makes perfect sense to me: if a bug exists in mozilla, it also exists in 
Netscape's commercial product. We try not to make very many bugs confidential. 
Sorry for the inconvenience.

Comment 6

18 years ago
> It makes perfect sense to me: if a bug exists in mozilla, it also exists in
> Netscape's commercial product.

Following that, we can as well "classify" nearly every other bug.

> Sorry for the inconvenience.

This is not so much an issue of convience, but more a matter of values or just
to be able to do work on Mozilla (bugtracking in this case).

Fortunately, there's a non-confident bug for this problem: bug #27242. I'll mark
DUP of  this one.

Lisa, thanks for the hint.
Status: VERIFIED → REOPENED
Resolution: DUPLICATE → ---

Comment 7

18 years ago

*** This bug has been marked as a duplicate of 27242 ***
Status: REOPENED → RESOLVED
Last Resolved: 18 years ago18 years ago
Resolution: --- → DUPLICATE

Comment 8

18 years ago
Marking verified as a duplicate.

Comment 9

18 years ago
Marking verified as a duplicate.
Status: RESOLVED → VERIFIED
(Assignee)

Comment 10

18 years ago
> Following that, we can as well "classify" nearly every other bug.

No, only the ones involving confidential features. Believe me, I don't like 
confidential bugs or confidential code. They make my life harder. However, the 
business needs are what they are, and we minimize the confidential bugs.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.