Bugzilla

The failures only seem to happen for `test_no_browsing_context` tests across all supported commands. These tests open a new tab, load a frameset, switch to the inner-most frame and then delete this active frame by clicking a link. In the failing cases the click event is never received by by the element, and as such the frame is not removed. This results in a timeout of the TimedPromise when waiting for flushing the event loop:

https://searchfox.org/mozilla-central/rev/da6a85e615827d353e5ca0e05770d8d346b761a9/remote/marionette/interaction.js#407-434 

Given that this code actually doesn't throw but only prints a log message the next WebDriver command will then fail.

I was not able to reproduce the problem locally yet and I wonder if this might be a race condition by not waiting long enough for the tab be fully ready.

The failures only seem to happen for `test_no_browsing_context` tests across all supported commands. These tests open a new tab, load a frameset, switch to the inner-most frame and then delete this active frame by clicking a link. In the failing cases the click event is never received by by the element, and as such the frame is not removed. This results in a timeout of the TimedPromise when waiting for flushing the event loop:

https://searchfox.org/mozilla-central/rev/da6a85e615827d353e5ca0e05770d8d346b761a9/remote/marionette/interaction.js#407-434 

Given that this code actually doesn't throw but only prints a log message the next WebDriver command will then fail.

I was not able to reproduce the problem locally yet and I wonder if this might be a race condition by not waiting long enough for the tab be fully ready. As such I pushed a try build to check if the click might  be delayed but that's not the case and even after 5s no `click` event has been received:

https://treeherder.mozilla.org/jobs?repo=try&revision=d0ebcd65392f535a16ce9d672622b6fc533e94ed&selectedTaskRun=UOsDkidmSSyyjGkuQktVZg.0

The failures only seem to happen for `test_no_browsing_context` tests across all supported commands. These tests open a new tab, load a frameset, switch to the inner-most frame and then delete this active frame by clicking a link. In the failing cases the click event is never received by by the element, and as such the frame is not removed. This results in a timeout of the TimedPromise when waiting for flushing the event loop:

https://searchfox.org/mozilla-central/rev/da6a85e615827d353e5ca0e05770d8d346b761a9/remote/marionette/interaction.js#407-434 

Given that this code actually doesn't throw but only prints a log message the next WebDriver command will then fail.

I was not able to reproduce the problem locally yet and I wonder if this might be a race condition by not waiting long enough for the tab be fully ready. As such I pushed a try build to check if the click might  be delayed but that's not the case and even after 5s no `click` event has been received:

https://treeherder.mozilla.org/jobs?repo=try&revision=f03cfe8ba5a65fa561dd68822e9b9e9518ae03fb&searchStr=wd