Seleniumbase wait_for_alert functions no longer work with chromedriver 76+ about seleniumbase HOT 10 CLOSED

I guess its not just ideal to be out of date, that said it seems to hold up ok :)

ChromeDriver 2.46
Supports Chrome v71-73

from seleniumbase.

I don't think its necessarily faulty; just W3C more-so compliant which will be the case going forward

from seleniumbase.

In the latest version of SeleniumBase, which is 1.30.0, “seleniumbase install chromedriver” installs chromedriver 2.44, which works fine with the latest version of chrome with no issues. Also, I’m in Europe right now for my honeymoon (currently getting WiFi at Hard Rock Cafe Mallorca), so I won’t be able to ship changes until August 30th. Try the latest SeleniumBase with “seleniumbase install chromedriver”.

from seleniumbase.

note: chromedriver 2.44 won't work with chrome 76+ correctly

from seleniumbase.

What issues did you experience with chromedriver 2.44 on Chrome 76? (I’m traveling through Italy now. Responses will be very delayed.)

from seleniumbase.

If the Chrome team ships a faulty chromedriver, that’s out of my control. I made it work by using an earlier one with the latest Chrome. Auto-accepting alerts leads to unexpected behavior. If a test needs to check that the alert appeared, the alert shouldn’t be auto-accepted or auto-dismissed.

from seleniumbase.

@symonk Try seleniumbase 1.31.0 . I made fixes that should have fixed your issue. #364

from seleniumbase.

And SeleniumBase v1.31.1 fixes another big issue with maximizing windows. Upgrade to that.

from seleniumbase.

I'm closing this issue as resolved. Please upgrade to the latest version of SeleniumBase (which is currently 1.31.2). Then make sure you have the latest version of chromedriver: seleniumbase install chromedriver latest.

from seleniumbase.

Everything should be all good by now if you upgrade to the latest version.

from seleniumbase.