1851511 - Allow to send widget events by Remote Protocols from the content process

Status: RESOLVED WONTFIX

(Core :: DOM: Content Processes, enhancement)

Description

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

For bug 1848957 the event handling code in Marionette and the Remote Agent need to send widget events from the content process. This doesn't work right now because eg. in BrowserParent::RecvDispatchWheelEvent a check for Cu.isInAutomation prevents that and causes the browser to crash.

As discussed with Nika we should have a separate check for our Remote Protocols (Marionette and Remote Agent) beside the one for Automation, so that running tests with Marionette, and WebDriver tests in general will always work and that especially outside of our CI.

Comment 1

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

Attachment: Bug 1851511 - [dom] Allow to send widget events by Remote Protocols from the content process.

Remote protocols like Marionette and Remote Agent that are also
used for WebDriver tests need to be able to simulate events
as close as possible to the real user. As such widget events
will be used to allow user input emulation for both headful
and headless testing.

Hereby it is not enough to only check for Cu.isInAutomation
because WebDriver tests will be mostly run outside of our CI
systems, and both remote protocols cannot fulfill the requirements
for Cu.isInAutomation. Therefore a separate check is used.

Comment 2

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

After talking to Olli today we decided to not follow this proposal but instead get Marionette and Remote Agent to dispatch the events on the parent process. The meta bug for this work is bug 1851812.