Closed Bug 126077 Opened 23 years ago Closed 23 years ago

wrong colors in renderings

Categories

(SeaMonkey :: General, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 125795

People

(Reporter: mozilla, Assigned: asa)

References

()

Details

Attachments

(1 file)

Mozilla 0.9.8+
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.8+) Gecko/20020216

As I browse http://slashdot.org/ in another tab, I'm noticing that the article
titles sometimes get rendered in this magenta-ish color instead of the actual
white.  It seems to change based on whether I'm using the arrow keys or
pgup/pgdn to navigate.  When I reload the page and use down arrow, I tend to get
some titles where the top 3/4 of the title line is rendered in this magenta-ish
color, with the bottom 1/4 rendered in the correct white.  Also, the rendered
colors don't stay the same.  If a particular title was mis-rendered as megenta
on pgdn to the bottom, it is most times back to white on pgup back to the top.

Another interesting thing is that I can leave the Mozilla window alone and just
cover and uncover it with another window and the mis-rendering has changed. 
Sometimes it's still there and just different, sometimes it goes away and then
comes back, etc.

I'll try to find a good windows sshot prog so I can attach some pix
Also, the "direction" of the mis-rendered color is in line with the direction in
which that area was "uncovered" - so if another window covers/uncovers in
horizontal motion (covers by getting dragged to the left, uncovers by getting
dragged away to the right, then some portion of the heading may be the magenta
color and then after some vertical point it becomes correctly rendered.  This is
in line with the horizontal "lines" of misrendering that I saw when doing pgup/pgdn
I'm not sure how reproducible this bug is going to be for others, but I *think*
I notice the pattern that the mis-renderings don't seem to happen while the page
is still loading, only after its fully loaded.  Take this with a huge grain of
salt, YMMV, etc. - just hoping it may provide a clue.
Dupe of bug 125795
Agreed - looks like a dup.  I'd go ahead and mark it resolved/duplicate, but 
since I have an sshot here and don't see one for the other bug, I hesitate to 
do so.  Also, I've put a lot of description into this bug.  I just don't want 
these to get missed by developers since they may help isolate the cause.

Your thoughts, asa?  DUP is fine by me, of course, I just want the contents of 
this bug report to help the overall tracking of the root cause.
Dup it is.  Don't worry, James, if the developers need more information, a 
link to this report is included in bug 125795's report.  If a developer is 
having trouble reproducing bug 125795, QA can point them in the right 
direction easily enough.

Thanks for helping out!

*** This bug has been marked as a duplicate of 125795 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: