Closed
Bug 80409
Opened 24 years ago
Closed 24 years ago
Black background in transparent images while scrolling document.
Categories
(Core :: Graphics: ImageLib, defect)
Tracking
()
People
(Reporter: bugzilla, Assigned: pavlov)
References
()
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9) Gecko/20010505
BuildID: 2001050515
Using an ATI rage pro turbo, 4.11.2560 (8mb) at 800x600, 32 bit colour, some
images display incorrectly when the document is scrolled, with a black image
that seems to be the same as the original displayed (sometimes repeatedly)
behind the original image. If the image is half-on the screen, it seems to
'tear' at the interface between the half that is scrolled back on and the half
that never left. Other windows can be positioned over the artifacts to make them
go away.
This seems to be new for 0.9 . It may be related to bug 21981
Reproducible: Always
Steps to Reproduce:
1. Using an ATI rage pro, 4.11.2560 (and possibly others)
2. Go to www.everything2.com
3. scroll down so that the 'everything 2' logo leaves the screen.
4. scroll back up slowly.
5. everything 2 logo now has black artifacts behind it.
6. scroll down so that the 'everything 2' logo leaves the screen.
7. scroll back up quickly
8. no artifacts.
9. scroll down so that half of the 'everything 2' logo is on screen.
10. scroll back up slowly.
11. artifacts.
12. alt-tab to another window which covers the corrupted logo
13. artifacts go away in the region the window covered.
Comment 2•24 years ago
|
||
Changing QA contact
Assignee: kmcclusk → pavlov
QA Contact: petersen → tpreston
Comment 3•24 years ago
|
||
WFM
The image displays correctly for me.
OS: Win2k SP1
Moz Build: 2001051104 Win32 Talkback
User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9+) Gecko/20010511
Comment 4•24 years ago
|
||
This should be a dupe.
Please reopen if you disagree !
*** This bug has been marked as a duplicate of 77914 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•