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

RESOLVED FIXED in Firefox 68

Status

()

defect
P2
normal
RESOLVED FIXED
4 months ago
Last month

People

(Reporter: hsivonen, Assigned: hsivonen)

Tracking

(Blocks 2 bugs)

unspecified
mozilla68
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Fission Milestone:M3, firefox68 fixed)

Details

(Whiteboard: [fission-event-m2], )

Attachments

(1 attachment)

Assignee

Description

4 months ago

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).

Assignee

Comment 1

4 months ago

e10s analog of this bug: bug 1075670

Assignee

Comment 2

3 months ago

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
Assignee

Updated

3 months ago
Blocks: 1540630
Assignee

Updated

3 months ago
Assignee: nobody → hsivonen
Status: NEW → ASSIGNED

Comment 7

2 months ago
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

Comment 8

2 months ago
bugherder
Status: ASSIGNED → RESOLVED
Closed: 2 months 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.