1922077 - Enable async event dispatching (remote.events.async.enabled) by default

Status: NEW

(Remote Protocol :: Agent, task, P2)

Description

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

At a certain point when all events can be dispatched as widget (async) events we should consider turning the preference remote.events.async.enabled on by default. Maybe this should happen for Nightly builds first.

Comment 1

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

(In reply to Henrik Skupin [:whimboo][⌚️UTC+2] from comment #0)

At a certain point when all events can be dispatched as widget (async) events we should consider turning the preference remote.events.async.enabled on by default. Maybe this should happen for Nightly builds first.

We actually do not need the widget events to enable the first batch of changes for processing actions in the parent process. For widget events I'm going to add additional preferences for each input type, which will depend on the above preference's value.

Turning on the feature by default requires all known issues to be fixed. I'm certain that we can enable it for the next Firefox 135 train. As such lets move this bug into the M14 milestone.

Comment 2

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

Before enabling the feature we should do some quick performance checks in how much the extra IPC communication delays the processing of the action chain, but not in that detail as initially assumed via bug 1904859.