278583 - rectangle fails to repaint if scrolled off screen and then scrolled back on.

Status: RESOLVED EXPIRED

(Core Graveyard :: GFX: Win32, defect)

Description

[Dan]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

On one specific forum, sigforum.com which uses UBB, some threads will not render
properly. On initial load, the thread will appear normal; however, on scrolling
down and then back up to the top of the thread, a rectangle appears on screen
that does not appear to get repainted properly. 

The rectangle is present through resizing the window and switching tabs. It
disappears on a page reload.



I'm not sure if this is a firefox-specific error. I'm using WinXP SP2.

Reproducible: Sometimes

Steps to Reproduce:
1. Go to www.sigforum.com
2. Enter The Lounge
3. Click a thread
4.  Scroll down, and then scroll back up
5.  If problem has not appeared, go back to Lounge index and repeat steps 3-5. I
notice the problem about 5-10% of the time.

Actual Results:  
A rectangle that doesn't appear to repaint appears and behaves almost as an
element of the web page.

Expected Results:  
Page renders correctly.

I don't know if this is common on other UBB boards, but does not appear on any
of the phpBB boards I frequent.

See http://sigforum.com/eve/ubb.x?a=tpc&s=674608412&f=320601935&m=118108861 for
a minor, nontechnical poll and discussion.

Comment 1

[Dan]

Attachment: Image of problem

Comment 2

[Dan]

Attachment: After scrolling up and down

This shows what happens after scrolling up and down, and illustrates why I
think it may be a problem repainting the window.

Comment 3

[Boris Zbarsky [:bzbarsky]]

Is this an issue with a current trunk build?  Also, do you have smooth-scrolling
enabled?  If so, does disabling it help?

Comment 4

[Gervase Markham [:gerv]]

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:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 5

[Gervase Markham [:gerv]]

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.