60207 - View/Headers/Brief is missing

Status: NEW

(SeaMonkey :: MailNews: Message Display, enhancement)

Description

[Not interested in Mozilla any more]

View/Headers/Brief option is missing in the news program.
This is available in Communicator 4.x and above and it would
be nice to see it in Mozilla.

Comment 1

[R.K.Aa.]

missing on linux too. Used to be there a while back. Is it deliberatly removed?

Comment 2

[scottputterman]

yes. The menu item used to be there but it didn't work anymore, so it got taken
out. reassigning to mscott.

Comment 3

[R.K.Aa.]

Status New, OS: All.

Comment 4

[R.K.Aa.]

*** Bug 61736 has been marked as a duplicate of this bug. ***

Comment 5

[Peter Lairo]

The Mail Header should only show "Subject" and "From" as Default (Normal
setting). All other info (date & To) just waste space and should be in a
separate and collapsible pane.

Maybe even just having the Subject in its own pane would beenough; the others
could be collapsed to save space (particularly useful for newsgroups, but also
good for longer e-mails).

These fixed panes (that don't scroll with the message) take up enough valuable
space as it is.

Comment 6

[Peter Lairo]

this bug has been quiet for some time. Is someone working on it yet?
[e-mail] has not made any comments here yet although the bug is
assigned to him. Also, there is no milestone set yet. This seems to be a "low
cost - high benefit" bug.

Suggest that view/header/brief only show SUBJECT and SENDER (in that order).

Comment 7

[scottputterman]

This currently isn't planned for mozilla0.8.  I've changed the nomination to
mozilla0.9 so it gets properly triaged for the next milestone.

Comment 8

[Ninoschka Baca]

This is also a problem when a mail message is selected.

Comment 9

[Nathan Robertson]

In related news, View --> Headers --> All doesn't work either. I'm assuming this
is all part of the one issue.

I'm running moz0.9 on Linux.

Comment 10

[Joerg Sievers]

Also happens with current nightly [2001061905]and all themes :-(

Comment 11

[Not interested in Mozilla any more]

The new foldable message header would work for me as the brief setting.
(ie. the one line message summary with from, subject and date you get
when you collapse the meassage header on the Mac) If, that is, it's
folded status was remembered between program sessions.

Comment 12

[Not interested in Mozilla any more]

Now that the message header is foldable into a nice neat line, and it remembers
the setting between sessions of the program, I'm happy to close this bug. What
do you think?

Comment 13

[Peter Lairo]

Sure, although I still miss the ability to access attachments *without* the
collapsed header expanding. IMO this should be possible in a correct "Brief
Header". Your call though.

Comment 14

[Koike Kazuhiko]

Attachment: Patch

Comment 15

[Koike Kazuhiko]

I don't know why View/Headers/Brief was removed, but I've made a patch.

(1) Added [View]-[Headers]-[Brief] menu item.

(2) Change checkmark when pressed toggle button in header view.

(3) Call ToggleHeaderView() in MsgViewNormalHeaders() and MsgViewBriefHeaders().


ToggleHeaderView() should be changed when All Header mode is implemented.

Comment 16

[Dimitrios]

Adding for 4xp keyword

Comment 17

[Koike Kazuhiko]

*** Bug 87851 has been marked as a duplicate of this bug. ***

Comment 18

[Not interested in Mozilla any more]

Was the patch from comment #14/15 ever landed. I can't see it on the build I 
have, which is 0.9.8+ and so far after the date of the patch. I'm quite
happy with the new style foldable message headers for 'brief' functionallity.
If there was a menu item that activated that feature it would be better for 4.x 
compatibility. Has anyone any thoughts or should we just close this bug.

Comment 19

[Peter Lairo]

Proposed "look" of view - header - brief:

+-----------------------------------------------------------------------------+
| Subject: This must have enough space for looong subjects    |Attachments   ||
|    From: YoMama                  Date: 31.12.2929 at 16:45  |______________||
+-----------------------------------------------------------------------------+
|                                                                             |

This would make it half as many lines as the "normal" header (4 -> 2) and twice
as much as the (unusable, because subject line is nearly unreadably short)
collapsed header (1 -> 2).

The attachment handling may be a bit tricky. Either make it a drompdown menu
like before (not so great), or attempt to make it 2.1 lines tall by moving the
date/time to the left a bit and extending the attachmnts windows downwards (as
shown above).

BTW. Please notice the word "at" between date and time. This makes the two more
distict and more readable.

Comment 20

[Not interested in Mozilla any more]

The format looks good to me, as long as we keep the single line (colapsed)
version which works very well on a large monitor.

Comment 21

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 22

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 23

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 24

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 25

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 26

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 27

[Not interested in Mozilla any more]

I've moved on from Seamonkey to Firefox so someone else will have to take over this bug.

Comment 28

[Tony Mechelynck [:tonymec]]

View => Headers => Brief is missing on the main menu in both Mail and News, but "Brief" headers are available by clicking the widget (shaped as minus-in-a-square alternating with plus-in-a-square, or as ▼ alternating with ▶, depending on the theme being used) found left of "Subject:" near the top left corner of the headers (and possibly s/left/right/ in RTL locales)

I'm confirming this RFE (without voting for it) but also adding some CC who I think may decide to resolve it WONTFIX.

Comment 29

[Tony Mechelynck [:tonymec]]

P.S. Comment #28 above followed a check with
Mozilla/5.0 (X11; Linux i686; rv:2.0b8pre) Gecko/20101209 Firefox/4.0b8pre SeaMonkey/2.1b2pre - Build ID: 20101209025017