1766795 - Possible timeouts in "WebDriver:Navigate" after a remoteness change has been detected

Status: NEW

(Remote Protocol :: Marionette, defect, P3)

Description

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

Since we enabled Android wdspec jobs in CI we got some unexpected timeout failures during a navigation and it looks like that we miss to detect load events after a remoteness change happened:

[task 2022-04-27T22:47:29.511Z] 22:47:29     INFO - PID 15641 | 1651099649510	webdriver::server	DEBUG	-> POST /session/dfddb76d-afde-4ce8-a6f4-b952b74da74c/url {"url": "http://web-platform.test:8000/webdriver/tests/support/inline.py?doc=%3C%21doctype+html%3E%0A%3Cmeta+charset%3DUTF-8%3E%0A%3Cinput+id%3D%27a%27+value%3D%27b%27%3E&mime=text%2Fhtml&charset=UTF-8"}
[task 2022-04-27T22:47:29.512Z] 22:47:29     INFO - PID 15641 | 1651099649511	Marionette	DEBUG	0 -> [0,7,"WebDriver:Navigate",{"url":"http://web-platform.test:8000/webdriver/tests/support/inline.py?doc=%3C%21doctype+html%3E%0A%3Cmeta+charset%3DUTF-8%3E%0A%3Cinput+id%3D%27a%27+value%3D%27b%27%3E&mime=text%2Fhtml&charset=UTF-8"}]
[task 2022-04-27T22:47:29.521Z] 22:47:29     INFO - PID 15641 | 1651099649521	Marionette	TRACE	[39] Received event beforeunload for about:blank
[task 2022-04-27T22:47:29.534Z] 22:47:29     INFO - PID 15641 | 1651099649533	Marionette	TRACE	Remoteness change detected. Set new top-level browsing context to 41
[task 2022-04-27T22:48:19.831Z] 22:48:19     INFO - TEST-UNEXPECTED-TIMEOUT | /webdriver/tests/get_alert_text/get.py | expected OK

Maybe we detect that remoteness change too late and ignored the load events from the new browsing context?