1715932 - Make event retargetting machinery work across document boundaries

Status: NEW

(Core :: Layout, defect)

Description

[Hiroyuki Ikezoe (:hiro)]

GetClosest function calls IsAncestorFrameCrossDoc, I believe this can be (will end up being) replaced with IsAncestorFrameCrossDocInProcess. That said, I don't think our event retargetting machinery works as expected in fission.

So for example, given that there is a clickable element which is close to an OOP iframe and the iframe content has no clickable element, if a user touches somewhere inside the iframe but is close to the clickable element, we want the clickable element to be a retarget-ed element, but I guess it's not working as of now.

Comment 1

[Chris Peterson [:cpeterson]]

Hiro, you said (in the bug's comments) that bug 1733509 doesn't block Android Fission because the bug is reproducible on Android without Fission. Bug 1733509 is the only bug blocking this event retargetting bug, which is still linked to the Android Fission meta bug 1610822.

Is there other work for this bug besides bug 1733509, work that does need to block Android Fission?

Comment 2

[Hiroyuki Ikezoe (:hiro)]

There's no other bug for Fission. I would say this bug is the bug needs to block Android Fission. Thanks.

Comment 3

[Botond Ballo [:botond]]

(In reply to Hiroyuki Ikezoe (:hiro) from comment #2)

I would say this bug is the bug needs to block Android Fission.

When we last discussed this (see Nov 8 comment on FFXP-1795) we decided this should be a backlog item rather than a blocker for the release of Android Fission.

Comment 4

[Chris Peterson [:cpeterson]]

(In reply to Botond Ballo [:botond] from comment #3)

When we last discussed this (see Nov 8 comment on FFXP-1795) we decided this should be a backlog item rather than a blocker for the release of Android Fission.

Thanks. In that case, I'll remove it from our list of Android Fission blockers.