1817819 - Missing XULFrameLoaderCreated event when synthesizing a click on a link from marionette on Desktop

Status: NEW

(Remote Protocol :: Marionette, defect, P3)

Description

[Julian Descottes [:jdescottes]]

While investigating Bug 1816061, we noticed that Marionette will not trigger a XULFrameLoaderCreated event when clicking on a link with target=top nested in an iframe.

This can normally be reproduced on the following test page https://bug1816061-testcase.glitch.me/

Clicking on the link manually should generate a XULFrameLoaderCreated event. Simulating a click with Marionette on Desktop will not.

However, simulating a click with Marionette on Mobile, with Fission enabled, will still trigger this event.

We should investigate why we are missing this event and how we could have a more accurate event simulation here.

Comment 1

[James Graham [:jgraham]]

My first suspicion is that this could be related to dispatching the events in the child process rather than the parent, but I'm not sure.

Comment 2

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Julian, could you have a look what James suggested?

Comment 3

[Julian Descottes [:jdescottes]]

I assume we need the ability to dispatch events from the parent process to do that. Isn't this blocked on what we should implement on m12? If not, how can I test it?

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Julian I assume you are referring to the event listener in driver.sys.mjs? I added a dump statement there but whether emitting the event in the content nor parent process makes actually a difference. There is no output, and so I think that the problem is related to something else. But you could try yourself as well. Here is the testing patch: https://pastebin.mozilla.org/rAHCzghN.

Comment 5

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Given that this bug is lower priority lets wait at least for actions being able to emit async mouse events which is done on bug 1848958. We can then check if that will fix it and mark it being blocked on bug 1490268 if that's the case.