SeleniumLibrary 6.1.1

SeleniumLibrary 6.1.1 is a hotfix release with one bug fix - the incompatablitilty with Selenium v4.10.0+. More information is given below.

SeleniumLibrary 6.1.1 was released on Friday August 4, 2023. SeleniumLibrary supports Python 3.7+, Selenium 4.3.0 or higher and Robot Framework 4.1.3 or higher.

Most important enhancements

Fixed Selenium v4.10.0+ Incompatibility
Selenium v4.10.0 removed code that was labeled as deprecated which we did not catch before the release. As such it broke code particular around how the Open Browser keyword calls into selenium. This release is a targeted change to resolve that conflict. In particular if one is using a few particular arguments with the Open Browser keyword then it is recommended you verify you get the same results as before. Some of these you should not need to make any changes as we make those internally. But others we completely removed and you with need to update to get the same functionality. Let me walk through those argument now ..

If you use the service_log_path and/or executable_path argument, these are now passed different to the webdriver creation. We have strong confidence this was done properly but still want to be transparent a change was made there. If you find something amiss please open a support ticket.

If you use Firefox and the ff_profile_dir argument, this is now attached first to the options structure and passed along to the webdriver creation via options. Again for most users you should not see any issues. If, by chance, you are already setting the profile via options (ie Open Browser None Firefox options=profile=/path/to/profile/dir) and through the ff_profile_dir then you will get unexpected operation. I suspect the ff_profile_dir will overwride the other; but that is just a guess. Don't try to set it in two places at once. I recognize the change of profile into the options structure complicates the argument structure here (for example what is you want to pass a profile object?). It is not my intention nor do I even attempt to address that here. If you do use Firefox profiles and have some thoughts on how we can improve this, please reach out.

If you use desired_capabilities they are deprecated and removed completely by Selenium. SeleniumLibrary just ignores that you passed them in. We will, most likely in the next release just remove that argument, but I wanted to ease you into this as best as I could. This is not the place for a tutorial on what has been the way to do this but you can find plenty about that on either Selenium Grid documentation or vendors like SauceLabs or BrowserStack.

Finally if you do do anything beyond the basic Open Browser someUrl someBrowser it would be worthwhile that with this release you get similar expected results as with the previous 6.1.0 release. If you see some browser configuration settings that are not resulting in previous usage and can prove this release has something in error please raise a ticket.

See full details in release notes