Open mdobrzanski opened 1 year ago
I've added the project side
I've added the project side
https://github.com/SeleniumHQ/selenium-ide/pull/1569
May be this PR will help you
@smildlzj Is it possible to pass the delay to selenium-side-runner?
BTW I see it's a screenshot from selenium-ide. The homepage mentions browser extensions but there's also standalone selenium-ide. Which one is advised to use?
@mdobrzanski - In January, Chrome will change the manifest such that a recording / playback interaction needs to use their dev tools. They don't support dynamic string evals, which is basically the core of v3 (an eval-based Selenium emulation). v4 will be all that remains later in January. I hope that clarifies things.
🐛 Bug Report
It seems there's a problem with getting new window identifier.
The test is fairly simple it:
It works fine in Selenium IDE but fails in selenium-side-runner with no such window error or precisely
Operation timed out running command selectWindow:handle=${win701}:!
I did some debugging and found that the problem can be mitigated by slowing down
waitForNewWindow
webdriver.ts#L276My version of the method:
To me it looks like some racing condition. It happens only when more js is involved on the page. I suspect the
waitForNewWindow
is executed before the actual window is really opened. Thethis.driver.getAllWindowHandles()
returns only single handle because the window did not open yet.To Reproduce
Expected behavior
Find opened window so that it can be selected.
Project file reproducing this issue (highly encouraged)
Sorry it's not the simplest test and uses https://beta.slashdb.com but that's the easiest way to expose it without setting up an artificial web server.
Environment
OS: Ubuntu 22.04.1 LTS Selenium IDE Version: 4.0.0-alpha.30 Selenium SIDE Runner Version: 4.0.0-alpha.34 Node version: v12.22.9 Browser: Chrome Browser Version: 107.0.5304.121 (Official Build) (64-bit)