240948 - Tinted images offset

Status: RESOLVED INVALID

(Core :: Layout: Images, Video, and HTML Frames, defect)

Description

[Scott Craig]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7b) Gecko/20040316
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7b) Gecko/20040316

When selecting (highlighting) material on a page, often the tinted image is
incorrect.  Instead of a blue version of the image, a blue version of some other
portion of the page is shown in its place. However, if the images are
highlighted by moving the mouse in a certain way, the correct image appears.  It
seems to have something to do with the order of the images in the tables.  For
example, mouse button down with the pointer in the top left and move straight
down.  The images are replaced with material from the left side of the screen. 
But move the pointer through the images in the right order, and they render
properly.

Reproducible: Always
Steps to Reproduce:
1. Go to slashdot, say.  Left button down while pointer is to left of top banner ad.
2. Holding down button, move mouse pointer straight down left side of page. 
Notice changed images.
3. Start again at top left.  This time move pointer through images in left to
right, top to bottom order.  Images are correct.

Actual Results:  
Images are changed when highlighted.

Expected Results:  
Images should be tinted, but otherwise the same when highlighted.

Comment 1

[Stefan Borggraefe]

Could you attach a screenshot showing this bug?

Comment 2

[Scott Craig]

Attachment: Correct highlighting created by moving mouse judiciously.

As requested.

Comment 3

[Scott Craig]

Attachment: Incorrect tinting.

As requested.

Comment 4

[Stefan Borggraefe]

WFM with a Linux build from yesterday.

Looks like this could be a driver issue. What graphics card are you using? Could
you try to update to the latest driver version available for it?

Comment 5

[Scott Craig]

You were right.  It was the graphics driver.

I am using a nvidia tnt2 card.  I had been using the "default monitor" driver
that comes with windows.  It is the latest that MS offers.

I installed the nvidia "display drivers" package, and the problem disappeared.

Too bad it won't work with the default configuration, though.  I haven't noticed
any other problems with the old driver.  But is it worth inserting a workaround
in Mozilla to fix a problem created by MS?

Comment 6

[Stefan Borggraefe]

(In reply to comment #5)
> Too bad it won't work with the default configuration, though.  I haven't noticed
> any other problems with the old driver.  But is it worth inserting a workaround
> in Mozilla to fix a problem created by MS?

Bug 224279 is about similar problems, but with newer nvidia driver versions (see
last attachment in that bug). Perhaps you could leave a comment there about the
issue you saw, which driver version fixed it and which one you were using
before. Thanks! :-)

I'm not the one to decide whether a workaround for this is needed, but normally
it is better to avoid such hacks.

FIXED is the wrong resolution for this bug. This is either INVALID (meaning it
is not a bug in Mozilla) or a dupe of bug 224279 (which is probably INVALID,
too). I'm marking it INVALID for now.