Closed
Bug 292291
Opened 20 years ago
Closed 20 years ago
Dynamically changing an image in a DIV leaves major artifacts.
Categories
(Camino Graveyard :: Page Layout, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 294415
Camino0.9
People
(Reporter: candiazoo, Assigned: mikepinkerton)
References
()
Details
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050428 Camino/0.8+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050428 Camino/0.8+
1. Go here: http://www.quiet-reflections.com/gallery.php
2. Move your pointer over each of the thumbnails in sequence.
You will notice that the text and portions of the previous image remain, and
bits of the border around the images are missing. Sometimes if you go over the
same thumbnail twice (without passing another one in the process) it will clear
out the artifacts.
Reproducible: Always
Steps to Reproduce:
1. Go here: http://www.quiet-reflections.com/gallery.php
2. Move your pointer over each of the thumbnails in sequence.
Actual Results:
Images leave large pieces behind, text as well. It is as if the region is not
properly refreshed, only the area of the new image and new text.
The whole area of the DIV should be refreshed!
Lovely; another Camino-only layout bug (related to the "scrambling" bug
everyone's talking about in Camino's MozillaZine forum?)
It helps to scroll from LTR and then back RTL to see the artifacts "better."
Confirming in 20050427 and 20050428 nightlies; not present in the 20050429 Fx
trunk nightly.
This seems pretty bad, so pulling the camino0.9 ? flag, too.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: camino0.9?
Summary: Dynamically changing an image in a DIV leaves major artifacts. → Dynamically changing an image in a DIV leaves major artifacts.
| Reporter | ||
Comment 2•20 years ago
|
||
Sorry. :( Camino is my favorite browser! I'll just keep using 0.8.3 and check
back with the nightly builds every once in awhile. One IMPORTANT thing I failed
to note: I am using a -O2 build of camino.
| Assignee | ||
Updated•20 years ago
|
Flags: camino0.9? → camino0.9+
Target Milestone: --- → Camino0.9
Comment 3•20 years ago
|
||
(In reply to comment #1)
> Lovely; another Camino-only layout bug (related to the "scrambling" bug
> everyone's talking about in Camino's MozillaZine forum?)
I wouldn't doubt that the cause is the same or close.
Comment 4•20 years ago
|
||
Sorry for the bug-spam in advance...
This is working perfectly for me with an official nightly from two or three days
ago as well as a custom build from last night. This is *probably* another
instance of the scrambling bug, but for what it's worth, I'm not seeing that
anymore, either.
cl
| Reporter | ||
Comment 5•20 years ago
|
||
Is it possible that this is only a problem with optimized builds?
| Reporter | ||
Comment 6•20 years ago
|
||
Well, I just tried it with the latest nightly build, 2005042908 (0.8+) and it
still happens. Did you try against my referenced URL?
Comment 7•20 years ago
|
||
(In reply to comment #6)
> Well, I just tried it with the latest nightly build, 2005042908 (0.8+) and it
> still happens. Did you try against my referenced URL?
Yep, no problems here with an optimised build either.
cl
It's rather difficult to get a screenshot of this, since the "entire window"
shortcut [cmd-shift-caps-4, then space, then mouseclick] doesn't capture it,
and dragging to select the area forces a redraw when the grey "selected area"
hits the artifacts. But this screenshot captures a small remnant that wasn't
redrawn.
Camino 20050510 (0.8+), Mac OS X 10.3.9
| Reporter | ||
Comment 9•20 years ago
|
||
Here is an image I captured using GRAB. Came out perfectly. This demonstrates
how repainting is not happening properly on my Mac mini using May 09 -O2
compiled Camino.
| Reporter | ||
Comment 10•20 years ago
|
||
Damn. I'm a fool. Should have tried/thought of this before. The issue ONLY OCCURS WHEN CACHING IS
ENABLED! Either memory, or disk. I used CaminoPrefs to disable one, then the other, then both to try.
When both are disabled it works fine. It seems to not be simply a refresh bug, but a refresh bug in
conjunction with caching. Hope this helps.
Dupe of bug 294415 per explanation in bug 294415 comment 18.
*** This bug has been marked as a duplicate of 294415 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•