User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030520 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030520 I sent a message with a long To line (email@example.com) Whenever that message was selected in the top right pane (grid of message details), the right 2 panes are expanded, and refuse to be shrunk. This had the effect that I couldn't see much of what was in the left hand pane, the mail boxes. I moved the message to a folder other than Sent, and it still happened. When I reduced the header part of message to one line with the little triangle, thus hiding the To line, things were back to normal - the message panes automatically resumes their normal size, and allowed me to shrink them to a sensible minimum. Reproducible: Always Steps to Reproduce: 1. Send a message with a long To value 2. Select that message in the message list pane 3. Try to shrink the right-hand side message panes with the slider Actual Results: Couldn't shrink the message panes Expected Results: The message panes should have been able to be shrunk.
Hi, I also see Problems with Mozilla/5.0 (Windows; U; Win98; de-AT; rv:1.4b) Gecko/20030507 but I am not sure whether I understand clearly what your special problem is. I created a message with your "to-address", some subject, some text and an attachment. I stored it as a draft and looked to my drafts-folder. My problems: When I select the message in the thread-pane, the account-overview-pane at the left disappears more or less, and I can't resize it. Additionally, I can not see the attachment-pane nearby the button "Entwurf bearbeiten" Rainer
Status: UNCONFIRMED → NEW
Ever confirmed: true
I think that this might be a DUP of bug 91662, pls. see http://bugzilla.mozilla.org/attachment.cgi?id=107665&action=view Can anyone verify this suspect? Rainer
This bug seems similar to bug #91662
Assignee: mail → nobody
QA Contact: esther → message-display
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
Status: NEW → UNCONFIRMED
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
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.