Open
Bug 1351062
Opened 8 years ago
Updated 2 years ago
[e10s] mouse movements are captured in a wrong way if CSS 'transform' changes in iframe
Categories
(Core :: Layout, defect, P3)
Tracking
()
NEW
People
(Reporter: 684sigma, Unassigned)
References
Details
Attachments
(2 files, 1 obsolete file)
I have a problem with Firefox Beta 52. It also happens in Beta 53, Nightly 55. Doesn't happen in ESR 45. On some sites I noticed a very weird behavior: mouse movements are captured incorrectly, as if mouse cursor was placed in a different area. I experimented a bit, and created a working example of the bug. I'll check those sites once this bug is fixed. Here's how to reproduce the bug: 1. Open attached page 2. Click on the button, then immediately move mouse over iframe 3. Keep moving mouse up and down within iframe and right-clicking, but don't click on buttons. Result: buttons become hovered far away from mouse cursor; context menu appears far away from mouse cursor. Expected: normal behavior. I've added "[e10s]" in the summary, because it isn't reproducible if in Nightlly I disable "multiprocess". Please correct me if this logic is incorrect.
Has STR: --- → yes
Keywords: regression
Updated•8 years ago
|
status-firefox52:
--- → wontfix
status-firefox53:
--- → affected
status-firefox54:
--- → affected
status-firefox55:
--- → affected
I found a regression range in FF42: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=b0b3dcfa5557&tochange=d3228c82badd I think it's a side-effect of bug 1172239 with e10s enabled.
Comment 3•8 years ago
|
||
I'm hoping this is more of a Layout thing :)
Component: Event Handling → Layout
Updated•7 years ago
|
Updated•7 years ago
|
Flags: needinfo?(aschen)
Updated•7 years ago
|
Comment 7•7 years ago
|
||
Refresh the test case as iframe with src attribute in data URI format will be taken as unique, opaque origins. See bug 1324406.
Attachment #8851747 -
Attachment is obsolete: true
Updated•7 years ago
|
Keywords: regression
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•