Closed
Bug 208308
Opened 22 years ago
Closed 22 years ago
Mozilla Mail main window is retained in lower pain
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 194638
People
(Reporter: williamsca, Assigned: sspitzer)
Details
Attachments
(1 file)
58.94 KB,
application/zip
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.5a) Gecko/20030603
Build Identifier: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.5a) Gecko/20030603
Using the three pane setup with multiple mail accounts, I often keep my primary
mail account expanded, but keep the other mail accounts unexpanded. When I
expand one of the secondary accounts, read the mail that's in it, then use the
arrow to unexpand it, the Mozilla Mail window fills the entire right pane. I
then select the Inbox for the primary account (which is expanded) and get the
three-pane mode back, but the lower pane on the right side retains whatever text
from the Mozilla Mail window was there. Selecting a message from the upper
right pane will then clear the lower pane and display the text.
Reproducible: Always
Steps to Reproduce:
1. Expand primary mail account with arrow to left of account name
2. Expand a second mail account with arrow to left of second account name
3. Select the inbox for the second account and read a message
4. Use the arrow to the left of the second mail account to unexpand it
5. Select inbox for primary mail account
Actual Results:
Doing the above steps causes the lower portion of the right pane to still
contain information from the two-paned Mozilla Mail window.
Expected Results:
The lower right hand pane should be blank until a message is selected.
I am attaching a screen capture of my window after performing the above steps.
Reporter | ||
Comment 1•22 years ago
|
||
Comment 2•22 years ago
|
||
*** This bug has been marked as a duplicate of 194638 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•