265323 - scrolling up/down produces white and black spots on images

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Marius]

User-Agent:       Mozilla/5.0 (Windows; U; Win 9x 4.90; rv:1.7.3) Gecko/20041001 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (Windows; U; Win 9x 4.90; rv:1.7.3) Gecko/20041001 Firefox/0.10.1

Scrolling up/down with scrollweel mouse/ up-down arrows or scroll bar On
http://slashdot.org the slashdot themes/topics images that appear from
below/above screen are spotted with black and white spots and white lines (see
screenshot).

It looks like mostly pages with .gif images are affected.

Scrolling PgUp/PgDn does not produce any spots.

Right-clicking on any link OR opening a link on affected page in another tab OR
 minimizing and restoring FF OR switching to another tab and back re-draws all
the images and spots&lines disappear. 



Similar (?) bug 201198 produces only white *lines*.





 

Reproducible: Always
Steps to Reproduce:
1. opening slashdot.org
2. scrolling down with keyboard -> result
3. scrolling up with keyboard -> result

Actual Results:  
Slashdot topic images(pictures) have white and black spots and white lines on them.

Expected Results:  
images (pictures) Should be rendered without spots and lines.

Always reproducible on my AMD K6-2 300MHz 64 MB RAM, 8Mb ATI video, Windos Me
with Firefox and Mozilla
Firefox 1.0PR: Mozilla/5.0 (Windows; U; Win 9x 4.90; rv:1.7.3) Gecko/20041001
Firefox/0.10.1
Mozilla 1.7.3: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.7.3)
Gecko/20040910.

Similar (?) bug 201198 produces only white *lines*.

Comment 1

[Marius]

Attachment: Screenshot: black and white spots when scrolling

Comment 2

[Peter van der Woude [:Peter6]]

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20041020 Firefox/1.0

WFM

Comment 3

[Norman Baker]

I've seen this problem before, and not on Firefox. It's because you have a lower
end processor and memory.

Comment 4

[Marius]

(In reply to comment #3)
> I've seen this problem before, and not on Firefox. It's because you have a lower
> end processor and memory.

But this happens mostly with .gif images. .png renders perfectly. 

Comment 5

[Norman Baker]

Hm; thats wierd. Well, I dont know, then; sorry! (-:þ
Works for me, though...

Mozilla/5.0 (Windows; U; Win 9x 4.90; rv:1.7.3) Gecko/20041001 Firefox/0.10.1

Comment 6

[Jasper Lieber]

I can confirm this on my computer and mozilla setup.  And I added another
example of this at bug 201198.

Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7) Gecko/20040616, dell laptop 192MB
RAM, Celeron 366 

Comment 7

[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 8

[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.