Closed
Bug 171831
Opened 23 years ago
Closed 23 years ago
Blocked images leaving garbage behind
Categories
(Core Graveyard :: Image: Painting, defect)
Core Graveyard
Image: Painting
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: nnbugzilla, Assigned: bugzilla)
Details
Attachments
(1 file)
|
133.37 KB,
image/png
|
Details |
If an image is blocked on a page, today's Phoenix build (2002093008) seems to
leave corruption or garbage in its place instead of painting over it. I'm not
sure why, because the same build of Mozilla doesn't do it. Will attach an
example. Win98.
| Reporter | ||
Comment 1•23 years ago
|
||
Here's an example. Also seen earlier on www.bluesnews.com and other sites.
| Reporter | ||
Comment 2•23 years ago
|
||
Forgot to mention, I'm blocking images by simply copying the cookperm.txt file
from my normal Mozilla profile. I suppose it's possible this will cause
problems, but corrupted graphics shouldn't be one of them.
Comment 3•23 years ago
|
||
unable to reproduce with a build from this evening.
| Reporter | ||
Comment 4•23 years ago
|
||
I still see it with the 2002093015 build, on 2 other computers. The only things
in common between the systems is they're all running Win98.
| Reporter | ||
Comment 5•23 years ago
|
||
Actually, I'm seeing this with regular Mozilla now, but it's sporadic and
doesn't happen all the time. Changing Product->Browser. (I would think this
must be a dupe; I can't be the only one seeing this, can I?)
Component: General → Image: GFX
Product: Phoenix → Browser
Version: unspecified → other
Comment 6•23 years ago
|
||
I see it with Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/2002100214,
changing OS.
pi
OS: Windows 98 → All
Hardware: PC → All
Comment 7•23 years ago
|
||
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021108 (+ patches
101274, 101762)
Seems to work now.
pi
| Reporter | ||
Comment 8•23 years ago
|
||
Verified as WORKSFORME. I no longer see this, either.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•