New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Method switchTo().alert()
should throw NoAlertPresentException
#273
Comments
Also applies to confirm() |
@martybum agree. We must fix it in Selenide 3.4 |
@asolntsev any news on this? |
Hi! By the way, pull requests are welcomed. :) Andrei Solntsev 2016-11-08 17:27 GMT+02:00 Martyn notifications@github.com:
|
will investigate this one this weekend |
… NoSuchFrameException instead of TimeoutException
I opened a new pull request about this issue. Welcome any comments or suggestions! |
…exception #273 throw NoAlertPresentException, NoSuchWindowException, or NoSuchF…
since Selenide 3.1, it throws
TimeoutException
.Probably the same problem with methods
switchTo().window()
andswitchTo().frame()
The text was updated successfully, but these errors were encountered: