Closed Bug 1532901 Opened 2 years ago Closed 2 years ago

event.screenX and event.screenY are wrong inside out-of-process iframes

Categories

(Core :: DOM: Events, defect, P2)

defect

Tracking

()

RESOLVED FIXED
mozilla68
Fission Milestone M3
Tracking Status
firefox68 --- fixed

People

(Reporter: hsivonen, Assigned: hsivonen)

References

(Blocks 2 open bugs, )

Details

(Whiteboard: [fission-event-m2])

Attachments

(1 file)

Steps to reproduce:

  1. Apply the patch from bug 1530661 is not already landed
  2. Set fission.oopif.attribute to true
  3. Set gfx.webrender.picture-caching to false
  4. Set gfx.webrender.all to true
  5. Navigate to https://hsivonen.fi/fission-host.html
  6. In each of the iframes, click the button such that the click lands on the same part of the same letterform of the word "Button" (pick any point of reference in the glyphs) in each case

Actual results:
screenX and screenY are the same in each case.

Expected result:
Expected especially screenY to be substantially different in each case (as it is with fission.oopif.attribute set to false).

e10s analog of this bug: bug 1075670

When a TabParent receives the transformation matrix from bug 1530661, it should probably push a copy to the associated TabChild. To reduce IPC traffic, we might want to refine the mechanism introduced in bug 1530661 to make APZ only send matrices that it deems to have changed.

Priority: -- → P2
Blocks: 1540630
Assignee: nobody → hsivonen
Status: NEW → ASSIGNED
Pushed by hsivonen@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/6e52132e8482
Fix event.screenX and event.screenY inside out-of-process iframes. r=nika
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
Fission Milestone: --- → M3
You need to log in before you can comment on or make changes to this bug.