Root cause: TourHomePage.startTour() created the PageWithTour right after clicking the launch link, while the browser was still navigating (the link opens the target page with startTour=true, then the tour's JavaScript redirects to the same page without that parameter). The page-ready wait of the PageWithTour constructor could thus address the html element of a document being replaced, which Chrome reports as Node with given id does not belong to the document. The fix waits, using only the WebDriver current URL, until the final tour page is reached. Confirmed locally on Chrome with a forced experiment: the unchanged code fails with the CI exception, the fixed code passed 164 forced launches.
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.
