1528723 - image only partially redrawn on mouse exit

Status: RESOLVED INVALID

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

Description

[Michele Costabile]

Attachment: Java Quick Start Tutorial_files.zip

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0

Steps to reproduce:

In the enclosed web page, a mouse enter in the image, followed by a mouse exit cause, in almost all cases an unnecessary redraw of the image and the bug

Actual results:

trapezoid areas are left blank blank, as shown in the enclosed pictures. They are correctly redrawn upon a new mouse enter

Expected results:

I thinlk that redwawing is utterly unnecessary in this case and is caused by the refresh of the decoration. The image is decorated as anchor, since it can be clicked. Only the decration of the link should be redrawn.
In any case, the whole image should be redrawn.

Comment 1

[Michele Costabile]

I am using Firefox 65.0.1, 64 bi, on Windows Server 2016

Comment 2

[Michele Costabile]

Attachment: The image when drawn correctly

Comment 3

[Michele Costabile]

Attachment: The image with blank areas

Comment 4

[Paul_B]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0

Hi reporter,

Thank you for taking the time to add this report. However, I was not able to reproduce the mentioned behavior on any of the latest Firefox versions. I've tried to reproduce it on Windows 10, Windows 7, Mac OS 10.14 and Ubuntu 18.04, on the same web page that you encountered the problem (on all the images present there) and other web pages, but I did not manage to reproduce the issue described.

Is this issue reproducing for you only on Firefox or is it also encountered on other browsers?
Could you please retest this using the latest FF release and latest Nightly build (https://nightly.mozilla.org/) and report back the results? When doing this, please use a new clean Firefox profile, maybe even safe mode, to eliminate custom settings as a possible cause (https://goo.gl/PNe90E).

Comment 5

[Michele Costabile]

I did some more testing and here are the results:

• I still have the incorrect behaviour in nightly (67.0a1 (2019-02-25) (64-bit)).
• The bug disappears in both nightly and current if I restart in safe mode
• The bug is still present if I restart and reset Firefox settings.
• I have no extensions installed in all my browsers.

Comment 6

[Paul_B]

Given the fact that the issue seems to be related to something that is specific to your setup, could you please try to find a regression range using Mozregression tool?
Information on the tool is available at http://mozilla.github.io/mozregression/. Please don't hesitate to contact us if you encounter any problems.

Comment 7

[Michele Costabile]

I tried regression, but more or less every release I tried was somewhat buggy. I this it has more to do with my particular configuration of OS and display driver. My OS is Windows 2016 server and the display driver is this

Name Microsoft Basic Display Adapter
PNP Device ID PCI\VEN_8086&DEV_1902&SUBSYS_2B5E103C&REV_06\3&11583659&0&10
Adapter Type , (Standard display types) compatible
Adapter Description Microsoft Basic Display Adapter
Adapter RAM 0 bytes
Installed Drivers Not Available
Driver Version 10.0.14393.0
INF File display.inf (MSBDA section)
Color Planes Not Available
Color Table Entries 4294967296
Resolution 1920 x 1080 x 1 hertz
Bits/Pixel 32
Memory Address 0xDE000000-0xDEFFFFFF
Memory Address 0xC0000000-0xCFFFFFFF
I/O Port 0x0000F000-0x0000F03F
Driver c:\windows\system32\drivers\basicdisplay.sys (10.0.14393.1066, 55,00 KB (56.320 bytes), 04/06/2018 09:27)

Maybe bit blitting is not dependable or is interrupted for some reason.
To add insight, I sometimes see what I am typing in this form painted uniformly gray.

Comment 8

[Michele Costabile]

Attachment: Mozbug 2.png

This is how the text in the bugzilla forms appears at times.

Comment 9

[Michele Costabile]

OK. I have news. After I noticed I was using a basic display driver, I updated the display driver using a driver published by Intel

Name Intel(R) HD Graphics 510
PNP Device ID PCI\VEN_8086&DEV_1902&SUBSYS_2B5E103C&REV_06\3&11583659&0&10
Adapter Type Intel(R) HD Graphics Family, Intel Corporation compatible
Adapter Description Intel(R) HD Graphics 510
Adapter RAM 1,00 GB (1.073.741.824 bytes)
Installed Drivers igdumdim64,igd10iumd64,igd10iumd64,igd12umd64,igdumdim32,igd10iumd32,igd10iumd32,igd12umd32
Driver Version 23.20.16.4849
INF File oem3.inf (iSKLD_w10_DS section)
Color Planes Not Available
Color Table Entries 4294967296
Resolution 1920 x 1080 x 60 hertz
Bits/Pixel 32
Memory Address 0xDE000000-0xDEFFFFFF
Memory Address 0xC0000000-0xCFFFFFFF
I/O Port 0x0000F000-0x0000F03F
IRQ Channel IRQ 4294967289
Driver c:\windows\system32\driverstore\filerepository\igdlh64.inf_amd64_bb81181f97438612\igdkmd64.sys (23.20.16.4849, 11,91 MB (12.485.096 bytes), 13/12/2017 21:26)

after this system update, I cannot reproduce the bug anymore.

The problem, thus, was present in all the releases I tried with Mozregression and most likely caused by an unnecessary redraw onsequences of mouse out, mouse in on an image with an anchor. The problem was visible because a slow driver would not complete all the bit blitting it was asked.
Notably, this problem was not shown - with the same system configuration - by Explorer 11. I think it was not because IE11 has better ways of refreshing the image than Firefox, but, rather, because there is some more refreshing of the image, just because its border is updated on mouse out, since the image is highlighted as a clickable anchor on mouse enter.
I hope this can help you.

Comment 10

[Daniel Holbert [:dholbert]]

Thanks for the report and the updates.

It sounds like this was a bug in the display driver, then (which Firefox happened to trigger) -- I'm going to resolve this as INVALID in the sense that it's a bug in another product.