Right now the detection of alerts/dialogs happen in the parent process. We have to investigate if that is still the right approach or if we should listen for the appropriate events inside the child actor. Right now we have a certain amount of failures for Mn unit tests, which seem to be all related to race conditions.

The commands that have to be proven to work are:

WebDriver:AcceptAlert
WebDriver:DismissAlert
WebDriver:GetAlertText
WebDriver:SendAlertText

Also all other commands have to immediately return when a new alert/dialog gets opened.

If detection of alerts/dialogs are already happening in parent process, then that should suffice for Fission.

Tentatively tracking marionette-fission-mvp bugs for Fission M7 Beta milestone. We would like Marionette tests to work with Fission before we ride the trains to Beta.

Henrik, these alerts and dialogs are implemented in the parent process, so detection should already work. Are you seeing detection problems with Fission?

This is needed when we interact with the child actor and new alerts / dialogs are opened. In such cases the currently active command needs to be canceled. I will have to take a look at this very soon.

Having the work for execute script done first (see bug 1662460) would help a lot here given that this can be a long running command that can easily be used for testing this particular feature.

I did some investigation today and as it looks like we can handle that perfectly in MarionetteFrameParent::sendQuery(). So it will block the actor work too.

https://hg.mozilla.org/mozilla-central/rev/d2e059b9faf0