Open Bug 1904859 Opened 5 days ago Updated 4 days ago

Wait for events dispatched in the content process and assess performance

Categories

(Remote Protocol :: Agent, task, P2)

Product:
Remote Protocol
Component:
Agent
Type:
task
Points:
8

Tracking

(Not tracked)

People

(Reporter: whimboo, Unassigned)

References

(Depends on 1 open bug, Blocks 3 open bugs)

Details

(Whiteboard: [webdriver:m12])

To rule out race conditions when dispatching events from an action chain, especially when multiple actions run in parallel within a tick, we need to ensure that the required events are indeed dispatched. Event listeners must be installed in the content process to wait for the events to be processed by the browser and the related events to be emitted before returning to the parent process for further processing of the action chain.

Further we should try to minimize the performance degradation caused by the additional step of waiting for the event to be dispatched. We should compare the results with Chrome's timings to ensure the impact is kept as low as possible.

You need to log in before you can comment on or make changes to this bug.