Bugzilla

Dispatching events from the parent process will cause us to have to update the Actions module in certain ways. This bug covers the required work to prepare all the work as needed for widget level events.

Topics this bug should cover:

* Duplicate the shared Actions module to keep the logic for content vs parent process event dispatching completely separated.

* Allow to more easily enable and disable the feature by creating a new hidden preference (“remote.events.parent.enabled”) which defaults to “false”.

* Route all existing content-process event dispatching through IPC to the old Actions module. This approach will allow us to gradually transition to parent process event dispatching while ensuring that input sources that haven't been converted yet continue to function.

Dispatching events from the parent process will cause us to have to update the Actions module in certain ways. This bug covers the required work to prepare the code base for widget level events:

* Move the JSON deserialization and Actions processing code entirely into the parent process. Use the MarionetteCommandsActor for IPC communication to call specific EventUtils methods in the content process.