Migrating to Selenium selenium-4.34.0
Version selenium-4.34.0 introduces 1 breaking change. This guide details how to update your code.
Released: 6/29/2025
1
Breaking Changes
4
Migration Steps
14
Affected Symbols
⚠️ Check Your Code
If you use any of these symbols, you need to read this guide:
RemoteWebDriver.isDownloadsEnabledCapabilityType.ENABLE_DOWNLOADSAcceptInsecureCertsProxy (user context options)enable_webextensionsBiDiPermissionsHistoryUpdatedParams.timestampGreedySlotSelectorremote_connection.py attributeremote/webdriver.pyserver.pyFtpProxy.NET BiDi namespace (e.g., Selenium.WebDriver.BiDi)stylecop files (removed)Breaking Changes
●Issue #1
dotnet: Simplified modules namespace for end users, requiring updated import paths for Selenium .NET BiDi classes. Update your using statements to the new namespace.
Migration Steps
- 1Update .NET import statements to the new simplified namespace as per the breaking change.
- 2Replace any usage of the hard-coded capability string "se:downloadsEnabled" with CapabilityType.ENABLE_DOWNLOADS.
- 3Avoid using the deprecated java FtpProxy class; switch to the recommended proxy configuration.
- 4If using the removed stylecop files in .NET projects, delete them.
Release Summary
This release adds several new BiDi options and API enhancements, fixes numerous bugs, deprecates Java FtpProxy, and introduces a breaking namespace change in the .NET bindings.
Need More Details?
View the full release notes and all changes for Selenium selenium-4.34.0.
View Full Changelog