Closed Bug 1264765 Opened 8 years ago Closed 8 years ago

Small area near middle / bottom of Google Image result pages not responding to clicks

Categories

(Core :: Widget, defect)

Product:
Core
Component:
Widget
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID
Tracking Flags:
Tracking Status
firefox45 --- wontfix
firefox46 --- wontfix
firefox47 --- affected
firefox48 --- affected

People

(Reporter: jaws, Unassigned)

References

(
URL
)

Details

Attachments

(5 files)

Screencast of bug
2.22 MB, application/x-shockwave-flash
Details
Screencast of bug 2
5.58 MB, application/x-shockwave-flash
Details
Screencast of bug 3 (hg web)
1.77 MB, application/x-shockwave-flash
Details
device pixel ratio testpage
62.42 KB, image/png
Details
Same bug in Windows Explorer
1.41 MB, application/x-shockwave-flash
Details 
STR:
1. Maximize the window
2. Click this link for a Google search of "pacific standard brooklyn ny", https://www.google.com/#q=pacific+standard+brooklyn+ny
3. Click on the "Photos" on the right side to see pictures of the bar/restaurant
4. Move your mouse to the bottom of the window and hover over the thumbnails.

ER:
5. All of the images are clickable and the mouse has the hand/pointer icon at all times

AR:
5. There is a region that does not respond to clicks. DevTools Inspector doesn't show any element covering that area. This does not happen to apps other than Firefox.

I am running Firefox Nightly 2016-04-14 on Windows 10 Insider build 14316 with e10s on. I have seen this bug for a week randomly but now have a webpage that consistently reproduces it for me.
Using mozregression with the STR from step 1, I found this regressed between http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=b672877ed046&tochange=0f7261e288f2

Note that I am running on a HiDPI external monitor, and the bug only happens when Firefox is on the external monitor. It doesn't need to be maximized.

Here's another video that shows the region stays the same no matter where I move the window and how elements in the window have correct hover effects unless they are beneath this region, http://screencast.com/t/8qCtPUqIQW

The resolution of this display is 3840x2160

Likely cause: bug 844604
Blocks: 844604
status-firefox45: ? → ---
status-firefox46: ? → ---
status-firefox47: ? → ---
status-firefox48: affected → ---
Flags: needinfo?(jfkthame)
I can't reproduce it on a simplified page of data:text/html,<body%20onmousemove="document.body.textContent=event.clientX%20+%20',%20'%20+%20event.clientY"%20style=width:100%;height:100%;margin:0;cursor:pointer>
This sounds really weird! If you could come up with a reduced testcase, that would be awesome...
Flags: needinfo?(jfkthame)
Keywords: testcase-wanted
(Given that your simplified example from comment 4 didn't work, maybe there's an issue just with coordinates in certain specific APIs that the page happens to be using... but that's a wild guess at this point.)
Jonathan, is Graphics:Text the right place for this bug because of the regression range?
Component: Untriaged → Graphics: Text
Flags: needinfo?(jfkthame)
No, this isn't Graphics:Text;  more likely something in Widget, or maybe event-handling code at some level that talks to widget about coordinates, etc...  Moving to Widget for now, as that's probably a good place to start digging, at least.
Component: Graphics: Text → Widget
Flags: needinfo?(jfkthame)
Ok, I created a reduced testcase. I went back to Google Images and started hiding elements on their page (via display:none) and noticed that the footer is positioned via position:absolute.

This test case reproduces the bug for me,
data:text/html,<body><button style="position:absolute;cursor:pointer;bottom:0;left:40%;width:500px;height:200px;">click me</button>

Some of the button shows a hover state, while a good portion of it acts as though the mouse is not hovering the button. Here's a video of it, http://screencast.com/t/z3JnI5oi3vna
I can reproduce it on hg web too, though this time it is showing that items half-way up the screen are getting hovered.
Attachment #8741479 - Attachment description: Screencat of bug 2 → Screencast of bug 2
Overall, how are your displays arranged? I.e. what's the size and resolution of each of your displays, and how are they positioned in relation to each other? And which is the system's primary monitor?

If you load https://people.mozilla.org/~jkew/tests/devPixRatio.html in the window where you're seeing this issue, what does it report for the window's coordinates and device pixel ratio?

(So far, I haven't been able to reproduce this; but I don't have Win10 with a display of those dimensions at present, only Win8.1 -- though I wouldn't have expected this to be Win10-specific, but who knows...)
Flags: needinfo?(jaws)
I'm reproducing this on my laptop with no external displays attached. My Firefox window is maximized. My advanced display settings on Windows says that I'm running with a 2560x1440 (recommended) resolution.
Flags: needinfo?(jaws)
OK, thanks. I set my (8.1) system up very similarly, but still don't see the issue. So maybe it really is Win10-related; or maybe some other quirk of your system? (Have you tried a new profile? Checked for suspicious add-ons?)

Bogdan, could you please see if you can reproduce the bug here? Thanks!
Flags: needinfo?(bogdan.maris)
I can reproduce this is in a brand new clean profile.
I'm reproducing this bug now on Windows Explorer in the folder view for my desktop. This seems to be an OS/hardware bug of some sorts.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(jmathies)
Flags: needinfo?(bogdan.maris)
Resolution: --- → INVALID
I wonder if your mouse/touchpad/whatever drivers are confused. Anyhow, glad to know it's apparently not our bug!
This was fixed by Microsoft in Windows 10 Pro Insider Preview build 14352.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: