DESCRIPTION: The splitter bar between the Headers list and the Message pane can either be dragged or the button can be clicked to toggle it between two states: the bar in middle position, or bar at bottom, maximizing the header pane. I suggest there also be a button to maximize it for the message pane. I would find this useful when I encounter a large message or one enclosing a photo. STEPS TO REPRODUCE: 1. Open mailnews in 3 pane configuration. View a large message. ACTUAL RESULTS: No quick way to maximize message pane and nor later return it to its middle position, so have to drag bar. There is a way to maximize listing pane, and return it to middle position. EXPECTED RESULTS: I suggest the splitter operate like a java JSplitPane, where the split bar has 2 buttons (up and down) which shift between 3 positions (top, middle, bottom). When at an extreme position (top or bottom), it takes two clicks to reach the other extreme: one to reach the middle, the second to continue to the other extreme.
gekacheka: Is this bug still an issue for you? With the current design of the header pane, you can click the "twisty" next to the subject and reduce the header pane to a single line.
In 3-pane mode, I usually have the headings listing pane about 1/3 (~14 lines) and the message pane about 2/3 the height (~30 lines). Clicking on the splitter bar moves the splitter bar to the bottom so the headings listing pane takes the full height. I would like another button to click on the splitter bar so the message pane takes full height. Clicking on the twisty you mentioned gets me about 3 more lines of the message, but I would like to get the full ~14 or so additional lines currently in the headings pane. I can do so by dragging the splitter bar upward and carefully back downward again later, but it would be much more convenient to be able to simply click on the splitter bar. (I would probably use the "expand-message" button more than the current "expand-headers-list" button, but both directions are useful.)
MASS-CHANGE: 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
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420