Mail panes flash grey before repainting when resizing mail



Core Graveyard
15 years ago
10 years ago


(Reporter: Lewis Jardine, Assigned: Kevin McCluskey (gone))


Windows XP

Firefox Tracking Flags

(Not tracked)




15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030310
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030310

When resizing the mail panes ('|-' layout), the top and bottom right panes flash
grey for about a frame before being drawn. This only seems to happen if the pane
is being drawn a different size than it's been drawn before. This doesn't happen
all the time, but once it starts, it continues to happen after closing and
reopening mail window.

Reproducible: Sometimes

Steps to Reproduce:
(Not 100% positive on these)

1. Start mozilla
2. Open mail
3. Select a message, and resize panes while message is loading

Actual Results:  
Panes flash grey for a frame, before being drawn normally. Occasionally two
copies of separator bar can be seen on screen at once

Expected Results:  
Panes are drawn cleanly - resizing is smooth, and multiple copies are not drawn.

Happens with 1.3 second release candidate

Don't see this bug in 1.2

Comment 1

15 years ago
Seems similar to bug 196308, but doesn't seem to have such a drastic effect.
I see a similar effect when un-maximising and resizing the browser window.

Comment 2

14 years ago
WFM with Moz 1.7.3. Reporter do you still see this problem with the latest
nightly, or even 1.7.3? If not, this bug has probably been fixed and can be
closed. Thanks.

Comment 3

14 years ago
I can still reproduce this in 1.7.2 . Method used:

Start mailnews
Grasp separator between message list and preview pane 

M  | Message 
a  |  List
i  | 
l  |----- 
b  |   ^
o  |   \____this one
x  |
e  | Preview 
s  |  Pane

Wiggle up and down vigourously.
Preview pane does not appear to flash gray, but message list does.

Will confirm with the latest nightly once it finishes downloading.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.