Open Bug 151831 Opened 23 years ago Updated 16 years ago

scroll bar & split pane mail header feature request

Categories

(SeaMonkey :: MailNews: Message Display, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

People

(Reporter: bingalls, Unassigned)

References

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:1.0.0) Gecko/20020529 BuildID: 2002052917 Because of bug 150813 Bugzilla won't let me change my email address, so June 2002 may be the last month I can respond. This was mentioned in http://bugzilla.mozilla.org/show_bug.cgi?id=106358 but was not pursued, nor was it the focus of that bug, afaik. Mozilla needs scrollbars, when Email headers are viewed with View->Headers->All enabled. A splitter pane to resize would help, too. Both horizontal & vertical scrollbars are needed. Reproducible: Always Steps to Reproduce: 1. In Mail or News, choose View->Headers->All from menu 2. View an email or news item, and expand its header 3. Reduce Mozilla window to 640x480 size Actual Results: Info is clipped, and inaccessible
I see the same effect when I have View->Headers->All enabled and try to look to all headers in a message with many headers. I see only part of the headers (ones which go first) and have no ability to look at the others. Well, there is possibilty - save message to a file and look into it, but it is very inconvenient. I see the bug when Mozilla is full-windowed in 1024x768 screen, which is much more common than 640x468.
*** Bug 210697 has been marked as a duplicate of this bug. ***
See item 2 in bug #41994
*** Bug 224025 has been marked as a duplicate of this bug. ***
can someone please confirm this? Why is this such a great problem to implement? I would also say that this is not 'enhancement' but a normal bug. View all headers is useless for mails with many header-fields. You can't see all of them! Personally I would classify this as major.
Flags: blocking1.6b?
A possible workaround is having only a subset of headers displayed (via the Mnenhy addon) in which you're interested, but that doesn't really solve the problem.
I'm very sure the 'blocking' request will be rejected, for several reasons: o blocking means 'holding up a release' - this only happens for important fixes (crashes, dataloss) - this bug is an RFE, and therefore by definition not critical o Generally, even for crasher bugs, 'blocking' is only reasonable if there is visible developer activity on a bug, with a clear and plausible assessment of a time required for fixing the bug - there is no point in holding up a beta release for an indefinite time o Irrespective of the status as 'blocker', a patch most likely wouldn't get approval for checkin in the 'beta' stage, since you are suggesting a profound UI change, and those are too risky at this stage of the release cycle. Requesting 'blocker' status is definitely *not* a proper way of drawing attention to your pet bugs - it only wastes time for the triage people (drivers), who have to go through such requests and minus them.
Flags: blocking1.6b?
Confirming based on duplicates and number of people commenting, in order to get it on the radar.
Status: UNCONFIRMED → NEW
Ever confirmed: true
*** Bug 233208 has been marked as a duplicate of this bug. ***
*** Bug 236070 has been marked as a duplicate of this bug. ***
*** Bug 241965 has been marked as a duplicate of this bug. ***
Product: Browser → Seamonkey
This bug was opened in 2002 and remains visable even through Thunderbird 1.0. With modern anti-spam and mailing list systems throwing sometimes dozens of headers into a given message, it becomes more and more critical that this bug gets fixed throughout the mozilla.org suite, if for no other reason than the mere presence of a "View All Headers" mode invites its use by non-nerds who think that the feature will actually do what the menu suggests it will. The solution proposed in bug 154712 is so-so. See my comment #18 on bug 154712 for my proposed solution.
a workaround is the following: Add to your userChrome.css: #msgHeaderView { max-height: 7em !important; overflow: auto !important; } Maybe something like this should go to the mainline?
(In reply to comment #13) > Maybe something like this should go to the mainline? Bug 240313.
*** Bug 281108 has been marked as a duplicate of this bug. ***
Assignee: sspitzer → mail
*** Bug 329467 has been marked as a duplicate of this bug. ***
Assignee: mail → nobody
QA Contact: olgam → message-display
You need to log in before you can comment on or make changes to this bug.