Closed Bug 162911 Opened 23 years ago Closed 16 years ago

Alert window in front of three pane causes re-paint issues

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Windows NT
defect
Not set
major

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: vparthas, Unassigned)

Details

An alert(window) from another application appeared in front of the mail three pane window and when that was closed the repaint wasnt done resulting in the image of the previous alert being there in the three pane window. Windows 20020808 build(1.0 branch).
Steve, is this a one time occurrence or do you see this all of the time? I'm going to take a guess that this would have happened regardless of what window you have up. Do you believe this is a Mach V stopper?
I'm not sure how reproducible this is. I just had what I think is the same situation and it didn't happen. In my original case, the popup window was a calendar alert that obscured part of the folder pane and part of the thread pane. In the thread pane, the selected message was visible and partially obscured by the popup. When I dismissed the popup, the folder and thread panes stopped repainting themselves. When I scrolled the thread pane it woke up again.
Product: Browser → Seamonkey
Assignee: sspitzer → mail
QA Contact: olgam → search
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
Assignee: mail → nobody
QA Contact: search → message-display
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
Closed: 16 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.