Closed Bug 71130 Opened 24 years ago Closed 24 years ago

Mail/news reader Subject etc. header box does not scroll with message

Categories

(SeaMonkey :: MailNews: Message Display, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 47422

People

(Reporter: rw, Assigned: sspitzer)

Details

From Bugzilla Helper: User-Agent: Mozilla/4.76 [en] (Windows NT 5.0; U) BuildID: 2001030308 I am reporting a designed in "feature" as bug. When reading mail or news, the bottom window has a fixed width shaded section for Subject:, From:, Date:, To:, CC: etc. This does not scroll as the message text scrolls, so it reduces the ability of the user to read the message, and therefore engourages them to maximise the lower window at the expense of the upper. I see no reason for this box-like header at all - scrollable or otherwise. I am perfectly happy with the way N4.x displays and prints the headers. A related issue is that this box-like thing is printed. This involves shaded backgrounds, which means: 1 - The text harder to read. 2 - Toner or ink is wasted. 3 - On an ink-jet, printing takes longer - because the head has to traverse the wider box. 4 - On an ink-jet, this area of the page becomes a bit soggy. 5 - On all printers, this area becomes harder to annotate with a pen or pencil. I understand the desire to distinguish the headers from the body of the message, but the lack of scrolling means less screen space and so a severe impediment to usage. On the printed page, I think it achieves nothing and has quite a number of drawbacks. Reproducible: Always Steps to Reproduce: 1. Read an email or news item on screen.
This is a DUP. BTW: I like it the way it is, probably because I'm using the standalone msg window. Printing is not related.
This is a dup of bug 47422
*** This bug has been marked as a duplicate of 47422 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
marking verified as duplicate
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.