Downloads

Earlier Chrome versions

For earlier versions of Chrome, here are the versions of ChromeDriver that support it.

For more information on selecting the right version of ChromeDriver, see the Version Selection page.

ChromeDriver 148

Bug fixes

• DOM access: Fixed a crash that occurred when simulating a button click inside an iframe that was itself nested inside a closed shadow root. The JavaScript previously used to find the owner frame element ID couldn't pierce closed shadow roots; the new implementation directly uses the f.X.d.Y.e.Z format to resolve the frame (crrev.com/c/7594919, Bug: 469831357).
• Security: Reinforced Chrome argument sanitization to prevent a potential vulnerability involving positional argument injection (crrev.com/c/7695604, Bug: 494464734).
• Testing: Increased the kImplicitWait timeout for FindElement(s)WhileNavigating tests in commands_unittest when running under AddressSanitizer (ASAN). The default 3s timeout was insufficient for the retry loop to consume all mock errors under ASAN overhead, causing flakiness (crrev.com/c/7657276).

Internal changes and refactors

• C++ standards: Replaced superfluous includes of base/functional/callback_forward.h across //chrome .cc files, enforcing the use of callback.h when callbacks are actually utilized (crrev.com/c/7200285, Bug: 40318405). Moved logging::LoggingSettings from base/logging.h to its own header base/logging/logging_settings.h to improve compilation efficiency (crrev.com/c/7173024, relanding crrev.com/c/7160150 after revert crrev.com/c/7170750). Addressed various IWYU errors related to base/logging.h (crrev.com/c/7730403, Bug: 499476145).
• C++ standards: Replaced redundant map count(key) checks followed by lookups with more efficient find(key) iterator accesses (crrev.com/c/7705392, crrev.com/c/7693277, Bug: 452950815). Injected ThreadDelegate through the Thread constructor to improve encapsulation, and added a Restartable option to Thread to accommodate cases where threads need restarting (crrev.com/c/7696887, Bug: 40881604).
• Memory safety: Converted file-wide #pragma allow_unsafe_buffers to granular UNSAFE_TODO() macros across chrome/ (crrev.com/c/7132241, Bug: 409340989). Shortened IOBuffer->span().first() to IOBuffer->first() (crrev.com/c/7159119).
• Dependencies: Rolled the crossbench dependency, bringing in fixes for discovering locally built ChromeDriver binaries on macOS and Android (crrev.com/c/7673978).
• Testing: Re-enabled the module scheme in chromedriver_py_tests following fixes to the underlying build and testing infrastructure (crrev.com/c/7707960).

ChromeDriver 147

Bug fixes

• Testing: Added a hermetic regression test to verify that ElementClick correctly handles clicks over cross-origin iframes with overlay elements, specifically in site isolation scenarios. This ensures clicks are not erroneously routed into the embedded content instead of the visible overlay (crrev.com/c/7261984, Bug: 42321834, Bug: 42322220).

Internal changes and refactors

• C++ standards: Renamed URL decoding modes and functions to adhere to the Google C++ style guide, changing DecodeURLMode to DecodeUrlMode and DecodeURLEscapeSequences() to DecodeUrlEscapeSequences() (crrev.com/c/7593238). Introduced url::UrlEscapeDecoder to simplify the usage of URL decoding throughout the codebase (crrev.com/c/7610180). Removed superfluous build/branding_buildflags.h includes from //chrome files (crrev.com/c/7595125, Bug: 40318405). Removed the BUILDFLAG(IS_FUCHSIA) logic from //chrome, except within ChromeDriver (crrev.com/c/5485913, Bug: 41481724).
• Memory safety (spanification): Resolved UNSAFE_TODO markers in ChromeDriver utilities, migrating them to safe span-based implementations (crrev.com/c/7562602, Bug: 435317390).

ChromeDriver 146

Bug fixes

• Stability: Fixed a ChromeDriver crash that could occur while processing a command if the window closed concurrently (e.g., while waiting for a navigation to complete). The fix acquires a lock on the WebView object to prevent it from being disposed prematurely (crrev.com/c/7257074, Bug: 468228355).
• Security: Added an Origin header check for incoming WebSocket connections to the ChromeDriver HTTP server, preventing potential cross-origin hijacking (crrev.com/c/7538400, Bug: 478783560).
• Testing: Moved testWebviewDetactedDuringClick to the flaky filter, skipping it in all runs rather than just headless mode (crrev.com/c/7545378, Bug: 481485821).

Internal changes and refactors

• C++ standards: Renamed base::DictValue and base::ListValue to their modern equivalents (base::Value::Dict and base::Value::List) across //chrome (crrev.com/c/7515855, crrev.com/c/7514475, Bug: 478100525). Replaced uses of base::Contains() with std::ranges::contains() (crrev.com/c/7461026, Bug: 470391351). Migrated std::set and std::unordered_set to base::fixed_flat_set where appropriate (crrev.com/c/7521991, Bug: 473916362). Refactored out base::JSONReader::Read calls that didn't specify parsing options (crrev.com/c/6990988, crrev.com/c/6980533, Bug: 446188265). Replaced various base::JSONWriter::Write() calls with base::WriteJson() (crrev.com/c/6969134, crrev.com/c/6929101, Bug: 443929217). Cleaned up #include order (crrev.com/c/7366868). Migrated bug references in comments to use Buganizer IDs instead of Monorail IDs (crrev.com/c/7528268, Bug: 321899722). Renamed IS_OZONE_* build flags to SUPPORTS_OZONE_* for clarity (crrev.com/c/7535923).
• Memory safety (spanification): Replaced unsafe pointer usage with base::span in base/strings/utf_string_conversion_utils.cc (crrev.com/c/7496410, Bug: 439964610, Bug: 40284755). Spanified more base::File usages in //chrome tests (crrev.com/c/7489592, Bug: 435317390). Replaced memset with aggregate initialization across //chrome (crrev.com/c/6875520, Bug: 435317390). Converted remaining #pragma allow_unsafe_buffers to UNSAFE_TODO markers (crrev.com/c/7132241, Bug: 409340989).
• DSE Prewarm: Enabled the DSEPrewarm feature in fieldtrial_testing_config.json for macOS and Windows, as related ChromeDriver test flakiness was addressed (crrev.com/c/7489009, relanding crrev.com/c/7002185 after revert crrev.com/c/7452344). (Note: This reland was subsequently reverted again due to increased test runtimes on Windows (crrev.com/c/7517985, Bug: 478888140)).
• Diagnostics: Added caller location tracking to WaitableEvent and ConditionVariable trace events for better debuggability (crrev.com/c/7487755, Bug: 476408124).

ChromeDriver 145

New features

• Testing: Updated the run_py_tests.py testing framework to accept deterministic string tests of varying lengths (e.g., 53, 101, and 501 characters) targeting input, textarea, and contenteditable elements. This provides regression coverage ensuring no characters are dropped during long send_keys operations (crrev.com/c/7221410, Bug: 428116078).
• Testing: Added a specific test for the HTML <selectlist> element (crrev.com/c/7420729, Bug: 342889200).

Bug fixes

• Screenshots: Reverted the scaling of element screenshots, as the WebDriver specification doesn't prescribe scaling and it was inconsistent with other screenshot functions (crrev.com/c/7409603, Bug: 42323022).
• Testing: Fixed failures in testClientHintsDeviceNameIPhoneX and testClientHintsDeviceNameIPad by updating ChromeDriver test expectations to match recent correct values (for platform, platformVersion, model, and mobile fields) introduced in DevTools Frontend (crrev.com/c/7408699, Bug: 474179501).

Internal changes and refactors

• C++ standards: Migrated various usages of base::Contains() to std::ranges::contains() across //chrome (crrev.com/c/7411011, Bug: 470391351), including necessary formatting fixes (crrev.com/c/7247217). Refactored string parameters to std::string_view to avoid unnecessary string allocations when using substr() (crrev.com/c/7350716). Removed superfluous <map> includes from //chrome headers (crrev.com/c/7225838, Bug: 40318405). Corrected include ordering in some files (crrev.com/c/7366868). Replaced legacy BodyAsStringCallbackDeprecated callbacks in SimpleURLLoader usages with BodyAsStringCallback which utilizes std::optional instead of std::unique_ptr (crrev.com/c/7210000, Bug: 40258809).
• Testing: Relanded the InfobarPrioritization field trial configuration, including fixes to prevent crashes in ChromeDriver browser tests when handling pending infobars that haven't been added to the view hierarchy (crrev.com/c/7223590, Bug: 447176374). Relanded country and locale filtering for the Glic feature, which was previously reverted due to unrelated test failures (crrev.com/c/7245749, relanding crrev.com/c/7148759 after revert crrev.com/c/7233767, Bug: 454431875).

ChromeDriver 144

New features

• Permissions: Updated the SetPermission command to adhere to the latest W3C specification, using the current frame's URL (embedded origin) in addition to the top-level origin. This correctly configures permissions like storage-access that rely on the embedded context (crrev.com/c/7106801, relanding crrev.com/c/7093216 after revert crrev.com/c/7104484, Bug: 384959114).
• Testing: Added testMetadata (including the test name) to the ChromeDriver test upload payload to support the flakiness endorser when using structured test IDs (crrev.com/c/7124354, Bug: 456432041).

Bug fixes

• Target Lifecycle: Fixed a bug where ChromeDriver would stall if a parent frame detached while a child frame was waiting for a command response. ChromeDriver now explicitly transitively detaches descendant frames when a parent WebViewImpl is locked and marked detached during command processing (crrev.com/c/7080912, Bug: 438436830).
• Window Management: Disabled the backgrounding of occluded windows specifically for ChromeDriver sessions. This resolves issues in WebDriver BiDi where tests could fail if the browser incorrectly deemed a window occluded and throttled it (crrev.com/c/7128058, Bug: 458027819).

Internal changes and refactors

• C++ standards: Removed superfluous includes of base/functional/callback_forward.h across //chrome .cc files, enforcing the use of callback.h when callbacks are actually utilized (crrev.com/c/7200285, Bug: 40318405). Moved logging::LoggingSettings from base/logging.h to its own header base/logging/logging_settings.h to improve compilation efficiency (crrev.com/c/7173024, relanding crrev.com/c/7160150 after revert crrev.com/c/7170750). Migrated uses of base::HexEncode to the newer base::HexEncodeLower (crrev.com/c/7103100, Bug: 456472080).
• Memory safety (spanification): Migrated WriteToPipe and WriteToPipeNoBestEffort in PipeBuilder and PipeConnection unit tests to accept base::span, fixing unsafe buffer usage (crrev.com/c/7090293, Bug: 455758227). Converted file-wide #pragma allow_unsafe_buffers to granular UNSAFE_TODO() macros across chrome/ (crrev.com/c/7132241, Bug: 409340989). Shortened IOBuffer->span().first() to IOBuffer->first() (crrev.com/c/7159119).

ChromeDriver 143

Bug fixes

• Stability: Fixed a Use-After-Free (UAF) crash within OverrideNetworkConditions. The raw pointer saved for subsequent application would get freed between back-to-back calls; it is now managed properly (crrev.com/c/7047422, Bug: 42323833).
• Testing: Fixed flaky Android ChromeDriver touch tests by utilizing the WaitForCondition API for more reliable synchronization (crrev.com/c/6978928, Bug: 42321861).
• DSE Prewarm: Disabled the Prewarm feature in ChromeDriver by default via the --disable-features=Prewarm switch, preventing prewarmed pages from interfering with test execution and target discovery (crrev.com/c/7007072, Bug: 431928370).

Internal changes and refactors

• C++ standards: Swapped ref_counted.h for scoped_refptr.h in //chrome headers where only the smart pointer is used, improving compilation efficiency (crrev.com/c/7080753, Bug: 40245294). Migrated GURL accessors to their Get* variants (e.g., GetSpec() instead of spec()) to clearly indicate string allocation, deterring accidental performance penalties (crrev.com/c/7002119, Bug: 448174617).
• Testing: Removed redundant check patterns in devtools_client_impl_unittest.cc using ADD_FAILURE() (crrev.com/c/6998270). Added a regression test for crbug.com/413382905 (crrev.com/c/6879417).

ChromeDriver 142

New features

• Diagnostics: Added the TERMINATION_STATUS_EVICTED_FOR_MEMORY status to differentiate processes proactively terminated by the browser (to save memory) from processes that crashed due to out-of-memory (OOM) errors. Currently, this behaves identically to an OOM crash (displaying a sad tab), but lays the groundwork for future distinct handling (crrev.com/c/6991933, Bug: 394092280).
• Diagnostics: Added the goog:processID capability to the WebDriver response, which returns the main process ID of the desktop browser. This brings ChromeDriver into alignment with Firefox's moz:processID and assists in testing platform accessibility APIs (crrev.com/c/5825307, Bug: 438884256).
• Testing: Added support for structured test ID uploads to ResultSink for ChromeDriver's Python integration tests (crrev.com/c/6916708, Bug: 418015486).

Bug fixes

• Diagnostics: Modified ChromeDriver's behavior upon a normal Chrome exit to no longer emit a confusing, generic error message related to user-data-dir usage. It now explicitly states that the instance was terminated and directs the user to the verbose logs for the specific error thrown by Chrome (crrev.com/c/6977507, Bug: 42323434).
• Initialization: Updated ChromeDriver's initialization structure to remain compatible with Selenium WebDriver v4.16.0 changes (crrev.com/c/6630600).
• Android: Fixed CheckAppInstalled on legacy Android versions (older than Android 11) where the --user cur flag is not supported by the package manager (crrev.com/c/6785949, Bug: 433885051).
• Testing: Fixed a bug where IgnoreDuplicateNavs was incorrectly overriding default capability switches in ChromeDriver. The feature has been disabled for ChromeDriver sessions, and the Switches::SetFromSwitches logic was corrected (crrev.com/c/6949166, Bug: 445332809).

Internal changes and refactors

• C++ standards: Replaced several deprecated base::JSONWriter::Write() calls with base::WriteJson(), maintaining the behavior of returning an empty string on failure when the return value wasn't checked (crrev.com/c/6969134, crrev.com/c/6929101, Bug: 443929217). Required explicit opt-in for non-compliant JSON parsing options (e.g., allowing comments) in base::JSONReader::Read and base::JSONReader::ReadAndReturnValueWithError (crrev.com/c/6990988, crrev.com/c/6980533, Bug: 446188265). Removed file-wide #pragma allow_unsafe_buffers pragmas following manual spanification efforts (crrev.com/c/6778035, Bug: 409340989). Cleaned up uses of the leaky LazyInstance macro (crrev.com/c/6781377, Bug: 432815283). Included missing headers for http_response_headers.h via IWYU (crrev.com/c/6894196, Bug: 40216326).
• Memory safety (spanification): Automatically spanified numerous pointers across the chrome/ directory for Linux builds, adding non-fatal CHECKs where size parameters were deemed redundant (crrev.com/c/6734592, Bug: 431824299).
• Testing: Temporarily disabled testDoesntCrashOnClosingBrowserFromAsyncScript on macOS (crrev.com/c/6995358, Bug: 446461733). Fixed typos in test method names involving "Certificates" (crrev.com/c/6950683). Auto-formatted //chrome/test GN files (crrev.com/c/6789277, Bug: 40760278).
• FedCM: Introduced a ShouldShowAccountsPassiveDialog function to IdentityDialogController to synchronously check if an accounts dialog should be shown, fixing a crash related to asynchronous checks and DevTools instrumentation (crrev.com/c/6780413, Bug: 425801332).
• DSE Prewarm: Added Page.setPrewarmingAllowed to the DevTools Protocol as a short-term solution to manually enable or disable prewarming, fixing related tests to ensure they interact with the primary page correctly (crrev.com/c/6847287, Bug: 431928370). Enabled the DSEPrewarm feature in fieldtrial_testing_config.json for macOS and Windows after resolving flakiness (crrev.com/c/6951835, Bug: 431928370, Bug: 435621391). (Note: The CDP command and the field trial enablement were both reverted due to being breaking changes for WebDriver users exposing unexpected targets, and causing other downstream issues respectively (crrev.com/c/6966133, crrev.com/c/6966161, Bug: 445883308)).
• Cleanup: Removed remaining references to the unsupported WebLayer project in Android code (crrev.com/c/6792520, Bug: 40272607).

ChromeDriver 141

New features

• Testing: Added support for the --enable-per-test-tracing flag to run_wpt_tests.py, matching the behavior of run_web_tests.py. This retrieves JSON trace events from an internal ChromeDriver buffer and saves them to the test results directory (crrev.com/c/6820247, Bug: 434017035).

Bug fixes

• Diagnostics: Prevented ChromeDriver from printing its own internal stack trace when returning a kTabCrashed error. This avoids confusing users, while still ensuring the renderer crash stack trace remains in the logs (crrev.com/c/6841669, Bug: 395131239).

Internal changes and refactors

• C++ standards: Replaced potentially unsafe memset calls with standard C++ aggregate initialization (instance = {}) across chrome/ to avoid bypassing constructors and ensure memory safety (crrev.com/c/6875520, Bug: 435317390). Added missing #include directives for //base/time/time.h via IWYU (crrev.com/c/6832689, Bug: 40216326). Rewrote forced unsafe buffer pragmas (crrev.com/c/6828538).
• Testing: Added a regression test for crbug.com/413382905 (crrev.com/c/6879417).
• View transitions: Relanded the view transitions fix updating work done before the finished promise is resolved, after an earlier speculative revert linked to ChromeDriver test failures was proven incorrect (crrev.com/c/6846765, relanding crrev.com/c/6806850 after revert crrev.com/c/6808537).

ChromeDriver 140

Bug fixes

• Target selection: Fixed an issue where the DevTools window could race with the main page to be selected as the primary window when Chrome was launched with --auto-open-devtools-for-tabs. ChromeDriver now explicitly excludes devtools:// prefixed targets during primary window determination (crrev.com/c/6769505, Bug: 427908560).
• Target selection: Prevented ChromeDriver from incorrectly calculating the in-view center point of elements by ignoring any overflow:hidden clipping imposed by ancestors. This aligns the calculation with the WebDriver spec and other PerformActions scenarios (crrev.com/c/6735230, Bug: 42322257).
• Android: Fixed the CheckAppInstalled function on older Android versions (pre-Android 11) where the --user cur flag for the package manager is not supported (crrev.com/c/6785949, Bug: 433885051).
• Testing: Fixed flakiness in the chromedriver_py_tests test suite caused by the DSEPrewarm feature. ChromeDriver now disables the prewarm trigger while a CDP client is attached to prevent unexpected target counts during tests (crrev.com/c/6764274, Bug: 423465927, Bug: 431928370).
• Testing: Reverted the addition of the ShouldShowAccountsPassiveDialog function to the IdentityDialogController (part of FedCM), which caused a regression (crrev.com/c/6780413, Bug: 425801332).

Internal changes and refactors

• C++ standards: Added missing std::vector #includes via Include What You Use (IWYU) (crrev.com/c/6652818, Bug: 40216326). Removed superfluous includes of gurl.h (crrev.com/c/6578272) and <queue> (crrev.com/c/6570349, Bug: 40318405) across //chrome headers. Addressed IWYU for NOTIMPLEMENTED() in //chrome (crrev.com/c/6655452, Bug: 41493641).
• Memory safety (spanification): Ran the automated pointer spanification tool across Linux builds, updating code to use spans where sizes are known (crrev.com/c/6734592, Bug: 431824299). Removed file-wide #pragma allow_unsafe_buffers pragmas across chrome/ following migration completion (crrev.com/c/6778035, Bug: 409340989). Excluded chrome/test targets from the -Wexit-time-destructors warning to allow enabling the warning globally (crrev.com/c/6736532, Bug: 40031409, Bug: 430332953). Cleaned up leaky LazyInstance usages under //chrome (crrev.com/c/6781377, Bug: 432815283).
• Cleanup: Removed the --debug-bidi-mapper CLI flag, as the transition to running the BiDi Mapper in a hidden target is complete and stable (crrev.com/c/6672011, Bug: 408992812).
• Cleanup: Removed remaining references to the unsupported WebLayer project (crrev.com/c/6792520, Bug: 40272607). Auto-formatted //chrome/test GN files to shorten target references (crrev.com/c/6789277, Bug: 40760278).
• Testing: Added an acceptance test to verify the fix for the PerformActions pointerMove issue (crrev.com/c/6648646, Bug: 42322257).
• Testing: Commented out the parallel driver creation segment of the testBrowserWithUsedUserDataDir test (and filed a tracking bug) as it caused failures on macOS related to exclusive locking when using chrome-headless-shell (crrev.com/c/6470455, Bug: 411407649, Bug: 380903149).
• Testing: Updated the run_cwt_chromedriver.py wrapper for iOS to support the --platform-type argument (crrev.com/c/6771517, Bug: 427548014).
• OWNERS: Removed nvitkov from the chrome/test/chromedriver/OWNERS file (crrev.com/c/6771413).

ChromeDriver 139

Bug fixes

• Initialization structure: Updated the ChromeDriver initialization structure to remain compatible with Selenium WebDriver v4.16.0 updates (crrev.com/c/6630600).
• Argument parsing: Coalesced multiple --js-flags arguments (similarly to how --enable-features is handled) instead of only taking the last one provided. This improves usability when passing complex V8 flags (crrev.com/c/6612042, Bug: 421941798).

Internal changes and refactors

• Memory safety (spanification): Replaced deprecated base::MakeStringPiece() usages with std::string_view across //chrome/test (crrev.com/c/6628089, Bug: 422940464). Included base/strings/string_view_util.h where base::as_string_view() is used, preparing for future namespace migrations (crrev.com/c/6625024, Bug: 423048781).
• C++ standards: Improved Include What You Use (IWYU) compliance across //chrome by explicitly including <vector> (crrev.com/c/6652818), base/notimplemented.h (and removing base/notreached.h where unused) (crrev.com/c/6655452, Bug: 41493641), base/strings/string_util.h (crrev.com/c/6607646), base/strings/string_number_conversions.h (crrev.com/c/6593576), and removing superfluous includes of base/debug/stack_trace.h (crrev.com/c/6622838).
• Testing: Ported the --driver-logging option to run_wpt_tests.py, allowing the script to dump ChromeDriver and browser stderr even at lower verbosity levels (crrev.com/c/6608138, Bug: 421262910).
• Testing: Re-enabled previously disabled ChromeDriver integration tests: screenshot tests (testTakeElementScreenshot*) (crrev.com/c/6598797, Bug: 42321815), window closing via Javascript tests (testCloseWindowUsingJavascript*) (crrev.com/c/6598978, Bug: 42321150), and headless-shell window size tests (crrev.com/c/6621336, Bug: 42323661).
• Testing: Fixed run_wpt_tests.py --stable to correctly identify and use the current stable version of Clank (Android) by parsing the APK, and updated the script to download the corresponding ChromeDriver version from Chrome for Testing (CfT) into a temporary directory rather than polluting the checkout (crrev.com/c/6635694, Bug: 402548382).
• Build infrastructure: Removed an unnecessary build dependency on write_build_config.py by disallowing android_resources() targets from having manifests, as manifest merging and R.java package naming are now handled by specialized attributes (crrev.com/c/6625266, Bug: 413331591).
• FedCM: Fixed a Finch config feature flag related to FedCM (crrev.com/c/6614137, Bug: 421959289).

ChromeDriver 138

New features

• Display feature management: Updated ChromeDriver behavior for viewport segments to match a recent CSS Working Group resolution: it now consistently returns an array with a single segment when a foldable device is used flat, or for all non-foldable devices. This matches media query behavior and mitigates fingerprinting risks (crrev.com/c/6469455, Bug: 414430842).
• Preferences & local state (Android): Added support for the localState and prefs capabilities when running ChromeDriver against Android devices. This relies on ADB and requires a custom user-data-dir flag; currently, it initializes the state with default templates (crrev.com/c/6397155, Bug: 406427226).

Bug fixes

• Stability: Fixed a ChromeDriver crash occurring on macOS when a user dismissed the First Run Experience (FRE) dialog via the "continue" button. The crash resulted from overriding a kTargetDetached error state and attempting to access an invalid WebView (crrev.com/c/6538867, Bug: 410599467).
• Performance testing: Fixed the crossbench test runner on Windows pinpoint bots which incorrectly tried to locate the ChromeDriver binary using an obsolete ../Release_x64 path when --browser=release_x64 was passed, causing it to fall back to downloading an older binary instead of using the local build (crrev.com/c/6502134).

Internal changes and refactors

• Memory safety (spanification): Replaced unchecked pointers in WebSocket::OnReadDuringHandshake and WebSocket::OnReadDuringOpen with base::span, addressing unsafe-buffer-usage warnings (crrev.com/c/6557346, Bug: 354307328). Removed unnecessary #pragma allow_unsafe_buffers pragmas across chrome/test/chromedriver that were no longer needed after other migrations (crrev.com/c/6503154, Bug: 414858406).
• C++ standards: Removed superfluous #include "url/gurl.h" and #include <queue> directives across chrome/ headers, adding forward declarations where appropriate to improve compile times (crrev.com/c/6578272, crrev.com/c/6570349, Bug: 40318405).
• API migration: Migrated RSAPrivateKey to crypto::PrivateKey and SHA256HashString to crypto::Sha256, cleaning up an obsolete error handling case since new key generation APIs are infallible (crrev.com/c/6490294, Bug: 372283556).
• Testing: Added the OwnContributionEstimate attribute to the Compute Pressure API automation commands (both CDP and testdriver implementations) (crrev.com/c/6373001, Bug: 402033762).
• Testing: Fixed integration tests verifying ClearDisplayFeatures on Continuous Integration (CFT) bots by simplifying assertions to check that the viewport segments are cleared back to the default viewport size (crrev.com/c/6535067, Bug: 417195296).
• Testing: Increased timeouts for Protected Audience WebDriver tests to address flakiness on slower CI bots (crrev.com/c/6494277).

ChromeDriver 137

New features

• Display feature management: Added ChromeDriver commands to emulate and clear display features, implementing the automation requirements for the Viewport Segments APIs (CSS and JS). This allows developers to programmatically test fold or hinge scenarios on dual-screen or foldable devices (crrev.com/c/6368674, Bug: 40137084).
• BiDi: Updated ChromeDriver to run the BiDi Mapper in a hidden target by default. This prevents the mapper's data:, page from interfering with test execution and visibility. To debug the mapper, clients can pass the --debug-bidi-mapper flag to run it in a visible tab (crrev.com/c/6441064, relanding crrev.com/c/6433672 after revert crrev.com/c/6439633, Bug: 402339952).

Bug fixes

• BiDi: Prevented ChromeDriver from incorrectly closing the entire browser session when processing BiDi commands (like browsingContext.close) if it lost track of targets created by other CDP or BiDi sessions. It now explicitly syncs top-level tabs before deciding to terminate the browser (crrev.com/c/6440293, Bug: 42323838).
• BiDi: Aligned with the upstream WebDriver BiDi specification by ensuring ChromeDriver removes the goog:channel capability if it is passed as an empty string, treating it identically to a missing channel (crrev.com/c/6438865, Bug: 409282307).
• Input: Fixed an issue where touch and pointer events failed or behaved incorrectly by updating ChromeDriver to support fractional (floating-point) x and y coordinates in pointer move commands (crrev.com/c/6440834, Bug: 409684333).
• Target selection: Prevented PDF out-of-process iframes (OOPIFs) opened in guest views (when the PdfOopif feature is disabled) from bleeding into the top-level targets list. The filtering logic was expanded to properly exclude these chrome-extension:// prefixed targets (crrev.com/c/6383500, Bug: 396611138).

Internal changes and refactors

• C++ standards: Relanded the change to use std::string_view for file names in LogMessage and trace events, resolving the issues with null-terminated string handling that caused previous reverts (crrev.com/c/6430129, relanding crrev.com/c/6395097, relanding crrev.com/c/6387020 after revert crrev.com/c/6383699).
• C++ standards: Modernized Environment::GetVar calls across //chrome to use the std::optional returning API instead of out-parameters (crrev.com/c/6417343, Bug: 400758498).
• C++ standards: Refactored Windows-specific handle helpers out of win_util.h into a dedicated windows_handle_util.h header to avoid circular dependency issues (crrev.com/c/6418805, Bug: 406023316).
• Testing: Added an Android-specific Browser domain handler and implemented the Browser.getWindowForTarget API to support Android window creation tests (crrev.com/c/6427605, Bug: 404932444).
• Testing: Fixed flakiness in macOS tests caused by extensions taking too long to initialize (crrev.com/c/6423229, Bug: 407804497).
• Testing: Temporarily disabled parallel user-data-dir creation in testBrowserWithUsedUserDataDir when running against chrome-headless-shell, as it conflicted with exclusive locking on macOS (crrev.com/c/6470455, Bug: 411407649, Bug: 380903149).
• Extensions: Updated Chrome tests to pass when the ExtensionManifestV2Unsupported field trial is enabled. This is a foundational step, though the trial itself remains disabled pending updates in other repositories (crrev.com/c/6415997, Bug: 367395349). (Note: A previous attempt to enable this trial via config was reverted crrev.com/c/6397497 reverting crrev.com/c/6358257).
• Dependencies: Manually rolled the catapult dependency and updated associated pydeps files and devil_util references (crrev.com/c/6480814, crrev.com/c/6466865, relanding crrev.com/c/6406098 after revert crrev.com/c/6448910, Bug: 397459590).

ChromeDriver 136

New features

• Browser lifecycle: Added a Chrome-specific capability quitGracefully that forces ChromeDriver to attempt to stop the browser gracefully (using Browser.close or SIGTERM) instead of the default SIGKILL. This gives debuggers like rr time to dump their recordings before the process terminates (crrev.com/c/6322538, relanding crrev.com/c/6269180 after a brief revert crrev.com/c/6320536, Bug: 339644807).
• Testing: Plumbed the run_wpt_tests.py --wrapper argument by generating a temporary wrapper script that prefixes the browser binary with the debugger (e.g., rr) and its arguments. This works around ChromeDriver's inability to substitute the binary directly when args are processed as switches (crrev.com/c/6271108, Bug: 339644807).
• Testing: Enabled translation by pref in TranslateEnabledTest to support a testing environment where ChromeDriver manages the browser process and bypasses the new --remote-debugging-port restriction when --user-data-dir is implicit (crrev.com/c/6354089, Bug: 327797500).
• DevTools: Added support for the DevTools multi-instance feature to open a new tab in another window on Android (crrev.com/c/6352169, Bug: 401269942, Bug: 382183406).

Bug fixes

• Target selection: Fixed an issue where PDF out-of-process iframes (OOPIFs) opened in guest views were not being filtered out from the top-level targets list when the PdfOopif feature was disabled. The filter was expanded to include the chrome-extension prefix, which resolves the bug and includes coverage for MV3 Chrome extensions creating tabs (crrev.com/c/6383500, Bug: 396611138).
• Target selection: Fixed a regression that caused the getWindowHandles() command to fail with a connection refused status when targeting packaged Chrome Apps (crrev.com/c/6317161, Bug: 396622746).

Internal changes and refactors

• C++ standards: Relanded the change that uses std::string_view for file names in LogMessage and trace events, improving compatibility with Rust logging structures that don't guarantee null-terminated strings (crrev.com/c/6387020, relanding crrev.com/c/5765705 after revert crrev.com/c/6383699 and another revert crrev.com/c/6395097).
• C++ standards: Replaced redundant base::Value::Clone() calls to optimize performance (crrev.com/c/6361818). Suppressed additional -Wunsafe-buffers-in-libc-calls warnings in Windows-specific files to clean up the build output (crrev.com/c/6369920, Bug: 390223051).
• Extensions: Reverted the addition of the fieldtrial_testing_config.json entry for the ExtensionManifestV2Unsupported phase due to an issue (crrev.com/c/6397497, reverting crrev.com/c/6358257, Bug: 367395349, Bug: 406523920).
• Documentation: Improved Android-specific ChromeDriver testing documentation (crrev.com/c/6354040).

ChromeDriver 135

New features

• BiDi: Updated the BiDi Mapper to inherit ChromeDriver permissions when --enable-unsafe-extension-debugging is specified. This enables WebDriver BiDi clients to effectively test extensions that require permissions typically held by the WebDriver client (crrev.com/c/6288627, Bug: 393500934).

Bug fixes

• Testing: Re-enabled and updated expectations for several WDSpec tests that were previously marked as failing. This restores spec conformance coverage for passing tests (crrev.com/c/6310420).

Internal changes and refactors

• Cleanup: Removed all traces of Lacros (including IS_CHROMEOS_LACROS and related test data) from chrome/test/ since Lacros is being deprecated, standardizing on IS_CHROMEOS (crrev.com/c/6284446, Bug: 354842935).
• Cleanup: Removed all traces of the md5sum utility following its replacement with devil_util, cleaning up legacy build dependencies (crrev.com/c/6309939, Bug: 397452007).
• C++ standards: Removed the chrome:: namespace from ResultCode and IsNormalResultCode(), moving them to the global namespace, and removed obsolete ChromeOS startup imports (crrev.com/c/6196899, Bug: 41050580).
• Memory safety: Simplified a std::lower_bound call in ChromeDriver by leveraging std::ranges::lower_bound (crrev.com/c/6223172, Bug: 392116519). Suppressed unsafe_libc_call warnings for initially identified non-compliant files in preparation for future enforcement (crrev.com/c/6187925, Bug: 390223051). Marked the return value of std::to_array as constexpr to improve safety and compile-time evaluation (crrev.com/c/6298909).

ChromeDriver 134

New features

• Bounce Tracking Mitigations (DIPS): Relanded ChromeDriver support for Bounce Tracking Mitigations, utilizing the RunBounceTrackingMitigations command. The integration test was restructured to use distinct pages, ensuring stateful bounces are correctly recorded before the command executes. This feature supports the nav-tracking-mitigations specification and is implemented in //chrome (crrev.com/c/4935955, Bug: 1474656). (Note: Originally added in crrev.com/c/4873672 and later reverted).
• BiDi: Updated ChromeDriver to use standard WebDriver BiDi extension properties with the goog: prefix, aligning with upstream chromium-bidi changes. The legacy channel property is no longer allowed (crrev.com/c/6179410).
• Windows: Added a version resource to the chromedriver.exe binary on Windows (crrev.com/c/6114586, Bug: 385300323).

Bug fixes

• MPArch/Targets: Fixed a regression where Chrome Extension targets (chrome-extension://) were being incorrectly discovered and attached to during primary target determination on ChromeOS, which caused subsequent commands (like navigation) to fail. Extension targets are now properly skipped during this initial phase (crrev.com/c/6183202, Bug: 385241097).
• MPArch/Targets: Fixed another regression where tab targets for Extension background_pages were not being properly filtered out from top-level web views when extension target support was disabled (crrev.com/c/6160774, Bug: 385731198).
• MPArch/Navigation: Fixed an issue where a tab could momentarily have no active page attached during an MPArch activation, causing ChromeDriver to incorrectly see it as an error state. ChromeDriver now waits for the tab to acquire a new page and complete its navigation before resolving the state (crrev.com/c/6177606).
• Log Processing: Fixed a crash (DCHECK failure in base::Value()) caused by improper truncation of log strings containing multibyte characters. The logic was updated to use UnicodeString boundary detection instead of simple std::string length checks, ensuring valid code points (crrev.com/c/6210809, Bug: 367752739).
• Testing: Migrated most prerendering-related WPTs (except for a few with known API issues) from content_shell to headless_shell, as the recent MPArch refactor allows ChromeDriver to run them correctly (crrev.com/c/6168830, Bug: 42323502, Bug: 366257368).

Internal changes and refactors

• C++ standards: Replaced usages of base::ranges with standard std::ranges (crrev.com/c/6200893, crrev.com/c/6177197, Bug: 386918226). Rewrote b ? "true" : "false" patterns to use base::ToString(bool) where possible (crrev.com/c/6165810, Bug: 335797528). Removed the unsafe StringPrintfNonConstexpr() function and replaced it with safer string formatting alternatives (crrev.com/c/6149756). Replaced pointer arithmetic (+ std::size) with standard begin/end iterators to resolve unsafe buffer warnings (crrev.com/c/6217045, Bug: 392116519).
• Cleanup: Removed the FedCmIdpSigninStatus feature flag and its runtime flag (crrev.com/c/6111321, Bug: 381211734). (Note: A previous removal attempt was reverted crrev.com/c/6082405 due to breakages).

ChromeDriver 133

New features

• Architecture: Refactored ChromeDriver to support Multiple Page Architecture (MPArch) and tab targets. WebViewImpl now connects to tab targets via AutoAttach. Commands that previously held a page now look for the active page under a tab. This change enables introspecting Extension background pages, which can now be targeted via the enable_extension_targets capability (by default, extension targets are skipped) (crrev.com/c/5961156, Bug: 379767670, Bug: 42323502). Fixed a regression where chrome-extension:// URL pages were incorrectly included as extension targets; selection is reverted to just type=background_page (crrev.com/c/6093588, Bug: 383141569). Moved enableExtensionTargets to Chrome Options instead of a top-level capability (crrev.com/c/6093032).
• Classic: Re-established support for multi-key element references. This undocumented feature, often used to create references compatible with both W3C and non-W3C modes, is now officially supported and covered by integration tests (crrev.com/c/6063257, Bug: 379584343).

Bug fixes

• Stability: Prevented ChromeDriver from blocking indefinitely when handling the browsingContext.close command. By using a different mechanism to determine if the browser needs to be closed, ChromeDriver can now properly handle beforeunload prompts without stalling (crrev.com/c/6080431, Bug: 42323838, Bug: 379049702).
• Navigation: Fixed a bug where a dummy page with the URL about:blank?test would cause a stall. The heuristic meant to identify an unresponsive new window (baseURL==about:blank and documentURL!=about:blank) now correctly handles these query-string URLs as a special case (crrev.com/c/6038039, Bug: 377410086).
• Navigation: Added logic to retry commands that fail with an AbortedByNavigation error. ChromeDriver will now attempt the command several times before giving up with a standard Timeout error (crrev.com/c/6012427, Bug: 42323825).
• Diagnostics: Forwarded the kTargetCrashed error directly through NavigationTracker. If a target crashes during navigation detection, this specific error is now surfaced to the user rather than a generic timeout, improving diagnostics (crrev.com/c/6032612, Bug: 377410086).
• Android: Fixed tab target lookups in chrome_android_impl.cc (crrev.com/c/6110492, Bug: 384781876).
• Testing: Fixed flakiness in several window-sizing tests on win11-arm64 (e.g., clicking on obscured elements). The tests now query the inner window size repeatedly after a resize operation until it correctly registers a positive height, accounting for slow window repaints (crrev.com/c/6012658, Bug: 378470046).
• Testing: Fixed multiple flakes in integration tests by mapping generic Python connection errors to WebSocketConnectionClosedException, simplifying error handling (crrev.com/c/6054134), avoiding race conditions by using SendCommand instead of PostCommand where immediate side effects are expected (crrev.com/c/6054137), and replacing reliance on immediate effects of ExecuteScript with more reliable navigation detection mechanisms (crrev.com/c/6063040, Bug: 42323825).
• Testing: Reverted the removal of the FedCmIdpSigninStatus feature flag, as its removal caused breakages (crrev.com/c/6082405, reverting crrev.com/c/6078693, Bug: 384866916, Bug: 381211734).
• Tools: Added support for the Print command in the log_replay script (crrev.com/c/6010809, Bug: 378451938).

Internal changes and refactors

• C++ standards: Removed Mojo.InvalidUTF8String histogram, allowing for the cleanup of public mojo headers and subsequent IWYU cascades (crrev.com/c/6133861, Bug: 40509710, Bug: 386793084).
• C++ standards: Avoided allocations in WaitableEvent::Wait() by switching from std::list to base::circular_deque (crrev.com/c/6097198).
• C++ standards: Defaulted user-defined empty constructors and destructors across the chrome/ codebase where possible (crrev.com/c/6101911, crrev.com/c/6056220, Bug: 381119547).
• Memory safety (spanification): Migrated C-style arrays to std::array across chrome/ as part of the broader effort to address -Wunsafe-buffer-usage warnings (crrev.com/c/6043879, Bug: 378069401). Plumbed strict size_t usage in span functions (crrev.com/c/6026238, crrev.com/c/6020621).
• Testing: Upstreamed fullscreen {ref,crash}tests back to wpt_internal/ as testdriver now supports them (crrev.com/c/6088404).
• Testing: Fixed wptrunner for iOS to correctly locate the ChromeDriver wrapper when using non-default output directories (e.g., //out/*-ios-wpt-fyi-rel/) by plumbing --build-directory correctly (crrev.com/c/6014940, Bug: 374199289, Bug: 355218109).
• Testing: Added the testBrowserCrashWhileWaitingForEvents integration test to demonstrate regression cases where fatal errors go unnoticed by clients (crrev.com/c/6025145, Bug: 379049702).
• Testing: Suppressed specific WPTs that crash when run under headless_shell combined with ChromeDriver to stabilize builders (crrev.com/c/6032163, Bug: 377410086).

ChromeDriver 132

New features

• Testing: Added support for the repeat and retry-limit command-line parameters to ChromeDriver integration tests, mapping them to the standard isolated-script-test-repeat and isolated-script-test-launcher-retry-limit arguments (crrev.com/c/5938195, Bug: 374681919). For tests executed locally (non-CI), the default retry-limit has been changed to 0 (crrev.com/c/5953326, Bug: 374681919).
• WebSockets: Implemented WebSocketConnection and related classes in EmbeddedTestServer, allowing WebSocket-related tests to migrate away from SpawnedTestServer. This includes framing according to the protocol and simplified handler registration (crrev.com/c/5849732, Bug: 40812029).

Bug fixes

• Stability: Fixed a ChromeDriver crash that could occur if a click command caused the browser to close, by properly handling the kTargetDetached error state introduced in earlier refactors (crrev.com/c/5934524, Bug: 42323264).
• Stability: Fixed an intermittent crash in the testClickNavigateRemoteToLocal integration test on Mac ARM64 by resolving a race condition (crrev.com/c/5975526, Bug: 375971185).
• Navigation: Fixed the GoBack and GoForward commands, which previously failed if Page.getNavigationHistory was called while the document was transitioning away from an active state (indicating an ongoing navigation). ChromeDriver now correctly retries the command in this scenario (crrev.com/c/6011739, Bug: 378433873).
• Script execution: Ensured that scripts which trigger a navigation or close a window correctly return a standard ScriptTimeout error if the browser side doesn't guarantee a result, prompting the user to avoid ambiguous test structures (crrev.com/c/5934265, Bug: 372883701).
• Script execution: Fixed an issue where the log replay functionality failed with an "unexpected command response" error (crrev.com/c/5961142, Bug: 42323342).
• Error codes: Corrected ChromeDriver's error handling to no longer forcefully wrap all exceptions with a "code" property into a generic "javascript error". This ensures standard errors like "stale element reference" (from call_function.js) and "invalid element state" (from the Selenium Atoms CLEAR function) are accurately propagated to the user (crrev.com/c/5937893, Bug: 42323409). Improved error handling in GetElementTagName to correctly interpret missing tag name information as "object is not an Element" (crrev.com/c/5929087).
• BiDi: Fixed an issue where BiDi sessions failed to initialize when a custom user profile was used. The custom profile's loaded page could prevent the BiDiMapper from starting; ChromeDriver now ensures the first tab always loads data:, to provide a clean slate for the mapper (crrev.com/c/5960656, Bug: 366886096).
• Incognito mode: Fixed a bug preventing ChromeDriver from creating new tabs while operating in Incognito mode (crrev.com/c/5952980, Bug: 42323352).
• Testing: Fixed flakiness in the testScriptNavigateRemoteToLocal integration test (which was failing at an 8.33% rate) and added C++ integration tests to reproduce and verify the fix for the race condition (crrev.com/c/6010867, Bug: 378387680).
• Testing: Re-enabled numerous previously flaky integration tests on Mac (testWindowMinimize) and Windows (ChromeDownloadDirTest.testFileDownloadAfterTab, InvalidCertificateTest.*), and globally (testShadowDomFindElement, element screenshot tests). Temporarily moved flaky css/css-scrollbars/ WPT tests back to content shell from headless shell (crrev.com/c/5953708, crrev.com/c/5948803, crrev.com/c/5941351, crrev.com/c/5941098, crrev.com/c/5959254, Bug: 42323825, Bug: 40848017, Bug: 40736504, Bug: 40176424, Bug: 40927590).

Internal changes and refactors

• BiDi: Bumped the chromium-bidi mapper dependency to incorporate the latest upstream fixes and protocol updates (crrev.com/c/5953339, crrev.com/c/5865478, Bug: 4226). (Note: A mapper bump was briefly reverted due to WPT failures and subsequently relanded (crrev.com/c/5961113)).
• Architecture: Minimized the usage of the thread-local session object across ChromeDriver to prevent state-sharing bugs between tests and simplify explicit session handling (crrev.com/c/5978486, Bug: 42323555). Refactored C++ integration tests to use a shared test fixture (crrev.com/c/5971474, Bug: 42323555).
• Cleanup: Removed deprecated workarounds specific to the "old headless" mode, as the legacy chrome-headless-shell code is no longer present in Chrome (crrev.com/c/5961602, Bug: 42323387).
• Cleanup: Removed the unused java_tests.txt file, a remnant of the previously evicted ChromeDriver acceptance tests (crrev.com/c/5970994, Bug: 357737793).
• Testing: Added a C++ integration test to verify that ChromeDriver doesn't erroneously create parallel sessions with the same user-data-dir or bleed URLs between sessions, which could cause flakiness (crrev.com/c/5961137, Bug: 375312517).
• Testing: Ensured that temporary ChromeDriver instances spun up by integration tests are shut down as quickly as possible to free resources (crrev.com/c/5997970, Bug: 375974725).

ChromeDriver 131

New features

• BiDi: Bumped the chromium-bidi mapper dependency to v0.8.0, incorporating the latest protocol updates and bug fixes (crrev.com/c/5899240, crrev.com/c/5865478, Bug: 4226).
• DOM access: Added support for closed shadow roots in the GetElementShadowRoot command. Previously, this command returned a NoSuchShadowRoot error when attempting to access a closed shadow root (crrev.com/c/5923865, Bug: 372834222).
• DOM access: Implemented support for window and frame identifiers, allowing references to windows or frames (including OOP Iframes) to be returned from executed scripts for further dereferencing (crrev.com/c/5890437, crrev.com/c/5923555, Bug: 366272556, Bug: 40229283).
• WebAuthn: Expanded the WebAuthn automation API to include userName and userDisplayName properties (crrev.com/c/5905423, Bug: 367915823).

Bug fixes

• Input: Fixed a race condition with mouse clicks on remote frames by routing mouse events to the highest same-origin ancestor of the target frame, rather than simply sending them to the top-most frame (crrev.com/c/5836968, Bug: 42323535).
• Input: Corrected the timestamp format sent with the Input.dispatchTouchEvent command from milliseconds to seconds, fixing crashes in WPT pointer events testing (crrev.com/c/5924253, Bug: 360918166).
• Testing: Re-enabled numerous ChromeDriver tests on Mac (crrev.com/c/5923569, crrev.com/c/5922823, crrev.com/c/5921444, crrev.com/c/5920851, crrev.com/c/5921442) and Windows (crrev.com/c/5923955) as their associated flakiness failures are no longer reproducible.

Internal changes and refactors

• Memory safety (spanification): Replaced unsafe pointer usage with base::span in net::HttpUtil (crrev.com/c/5854420), and migrated base::File::WriteAtCurrentPos() to its span-based equivalent (crrev.com/c/5818972). Rewrote map pointer values (e.g., in std::map, std::unordered_map) to raw_ptr (crrev.com/c/5867189, Bug: 329428315).
• C++ standards: Replaced Abseil attribute macros (ABSL_ATTRIBUTE_*) with standard base/ macros (crrev.com/c/5852373). Avoided unintended copies by replacing pass-by-value strings/vectors with std::string_view or const references where appropriate, and removed stray const qualifiers from std::string_view arguments (crrev.com/c/5914620, crrev.com/c/5906184, Bug: 369952985).
• Infrastructure: Configured Fuchsia to use ChromeDriver to control web-engine (crrev.com/c/5867896, Bug: 40935291).
• Testing: Migrated a fenced frames WebAuthn test from the legacy content shell runner to headless Chrome with ChromeDriver, as the legacy runner will soon drop support for the WebAuthn testdriver API (crrev.com/c/5920770, Bug: 372169469).

ChromeDriver 130

New features

• BiDi: Bumped the BiDi Mapper dependency, fetching the latest protocol updates and bug fixes from upstream chromium-bidi (crrev.com/c/5850570, relanding crrev.com/c/5837065 after revert crrev.com/c/5840080; crrev.com/c/5717956, Bug: 4226).
• BiDi: Updated ChromeDriver to supply unhandledPromptBehavior directly to the Mapper via the session.new command when initializing a BiDi session. This completes the migration away from MapperOptions (crrev.com/c/5682934, crrev.com/c/5766077, Bug: 42323841, Bug: 356371297).
• Testing: Added support for the --chromedriver argument to the bisect-builds.py script for desktop builds, allowing the script to automatically download and use the correct version of ChromeDriver during bisections for WebDriver/ChromeDriver dependent tests (crrev.com/c/5861048, Bug: 352344089).

Internal changes and refactors

• C++ standards: Resolved "rule-of-five" issues in various classes. Because the Chrome style plugin insists on out-of-line destructors without also enforcing out-of-line move constructors, the compiler was implicitly deleting move operators and silently falling back to copies. These missing declarations have been added (crrev.com/c/5846757, Bug: 364788123).
• Testing: Cleaned up the wptrunner test results summary by replacing the hardcoded chrome string with the actual product used and hiding the verbose command artifact from the summary output (crrev.com/c/5825633, Bug: 41494889).
• Testing: Fixed massive test failures in ChromeDriver integration tests on macOS 15 (Mac15) by doubling specific timeouts, as tests on this OS required significantly more time than on Mac14. Four virtual sensor tests were also added to the ignore list due to flakiness (crrev.com/c/5817455, Bug: 354939744).
• Testing: Disabled the flaky ChromeDriverSiteIsolation.testClickNavigateLocalToLocal test on Mac (crrev.com/c/5806894, Bug: 361521805) and the flaky ChromeDriverTest.testClickElement*ObscuredByScrollBar tests on Windows 11 (crrev.com/c/5804083, Bug: 360058651).
• Testing: Removed the ChromeDriver acceptance tests (which downloaded older Chrome versions to test against the current ChromeDriver) due to several infrastructure issues. They may be re-added later on CI with autoroll (crrev.com/c/5812142, Bug: 357737793).

ChromeDriver 129

New features

• BiDi: Updated the ChromeDriver session initialization helper to send a session.new command to the BiDi Mapper, allowing the mapper to directly handle capabilities. This is the first step toward removing MapperOptions (crrev.com/c/5741432, Bug: 356371297). (Note: A related change crrev.com/c/5754093 providing the processed unhandledPromptBehavior was reverted crrev.com/c/5755744 due to a drop in test coverage).
• Compute Pressure: Added new extension commands for virtual pressure source management, implementing the Automation section of the Compute Pressure specification. These commands are parsed and forwarded to the CDP layer (crrev.com/c/5666583, Bug: 347031400).
• Extensions MV2: Updated tests exercising MV2 behavior to use the ScopedTestMV2Enabler as part of the ongoing Extension Manifest V2 Deprecation field trial (crrev.com/c/5685054, Bug: 339061151).

Bug fixes

• Classic serialization: Tracked seen objects when serializing a Set in WebDriver Classic script execution results, preventing infinite loops and tolerating overrides of Array.prototype.includes (crrev.com/c/5765833, Bug: 357472850). (Note: This was subsequently reverted crrev.com/c/5773175 due to a WPT regression).

Internal changes and refactors

• BiDi: Bumped the BiDi Mapper dependency to include the latest bug fixes and protocol updates from chromium-bidi (crrev.com/c/5756587, crrev.com/c/5717956, Bug: 4226).
• Memory safety (spanification): Replaced unsafe buffer usage in WebSocketFrameParser::Decode, MaskWebSocketFramePayload, and WriteWebSocketFrameHeader with base::span (crrev.com/c/5764863, crrev.com/c/5743019, crrev.com/c/5722108, Bug: 40284755, Bug: 354307327). Added #pragma allow_unsafe_buffers across chrome/* as preparation for further fixes (crrev.com/c/5717950, Bug: 40285824), and converted non-conforming UNSAFE_BUFFERS() macros to UNSAFE_TODO() (crrev.com/c/5786346). Rewrote base::span fields to base::raw_span (crrev.com/c/5515096, Bug: 332587642).
• C++ standards: Removed the use of dangerous variable-length arrays (VLAs) in the codebase by explicitly marking array lengths as constexpr (crrev.com/c/5738737, Bug: 349656479). Included necessary <unordered_map> headers previously pulled in transitively (crrev.com/c/5792881).
• Architecture: Unforked the WebSocketEncoder implementation by reverting its stalled migration to //services/network/public/cpp/server and centralizing the logic back within //net/server to ensure consistent updates (crrev.com/c/5768214, Bug: 40205564).

ChromeDriver 128

New features

• Capabilities: Allowed the use of a dictionary for the unhandledPromptBehavior capability, aligning with standard capability structures, though it is not yet fully respected by the Mapper (crrev.com/c/5692204, crrev.com/c/5682934, Bug: 42323841).
• Startup: Added the --ignore-explicit-port command-line argument to ChromeDriver. This temporary workaround forces ChromeDriver to ignore any explicitly provided port and instead find and bind to a free port, resolving TCP port races during web platform test execution (intended to be removed after M132) (crrev.com/c/5724574, crrev.com/c/5703976, Bug: 42323836).

Bug fixes

• Sensors: Fixed the ExecuteUpdateVirtualSensor command to use SendCommand() instead of SendCommandAndGetResult(), as the setSensorOverrideReadings CDP command doesn't return a value (crrev.com/c/5703589).
• FedCM: Fixed a race condition in FedCM ChromeDriver tests by no longer asserting that NoSuchDialog is returned when a dialog is actually expected, preventing failures if the dialog appears too quickly (crrev.com/c/5713515, Bug: 346530330).
• Testing: Re-enabled WebAuthn virtual authenticator tests on Mac after the underlying issue (crbug.com/40233722) was fixed (crrev.com/c/5635806, Bug: 329130177).
• Error Messages: Fixed a typo in the error message for the execute/async command (crrev.com/c/5697913).

Internal changes and refactors

• BiDi: Bumped the BiDi Mapper dependency, bringing in the latest protocol features, bug fixes, and WPT expectation updates from the upstream chromium-bidi project (crrev.com/c/5717956, crrev.com/c/5644823, crrev.com/c/5630727, crrev.com/c/5615110, crrev.com/c/5614670, Bug: 4226, Bug: 347863537, Bug: 324436866).
• Replaced usages of the deprecated GrowableIOBuffer::StartOfBuffer method with span, improving memory safety by eliminating unchecked pointers (crrev.com/c/5706088, Bug: 329476354).
• Spanified the Decode methods of WebSocketFrameParser to improve memory safety (crrev.com/c/5722108, Bug: 354307327).
• Cleaned up remaining remnants of absl::optional by removing obsolete Abseil headers, migrating to std::optional (crrev.com/c/5691505, Bug: 40242125).
• Changed ChromeDriver to handle all unknown target types (including shared_storage_worklet) as WebViewInfo::kOther rather than treating them as errors. This allows Chrome to introduce new target types without immediately breaking WPTs (crrev.com/c/5680542, crrev.com/c/5679146, Bug: 42323839).
• Added an installer target for the linux-builder-perf builder to generate symbol-stripped binaries for bisect archives, and configured pinpoint builders to accept varying additional_compile_targets (crrev.com/c/5668198, Bug: 344643694).
• Updated run_performance_tests.py to find and pass the ChromeDriver location to crossbench during perf builds (crrev.com/c/5624538, Bug: 338629299).
• Rolled the crossbench dependency (crrev.com/c/5681849).
• Marked FedCmSpecificTest.testClickErrorMoreDetails and FedCmSpecificTest.testClickErrorGotIt as flaky on Mac (crrev.com/c/5704320, crrev.com/c/5677564, Bug: 352821422, Bug: 346530330).
• Disabled the flaky BidiTest.testFocusInFirstTab test (crrev.com/c/5676686, Bug: 350916212).

ChromeDriver 127

Bug fixes

• Stability: Fixed a ChromeDriver crash that occurred when a target.detachFromTarget command (or target.detachedFromTarget event) was received while the DevTools client was actively processing other commands, preventing the premature release of the WebView and DevToolsClient objects (crrev.com/c/5527584, Bug: 339773537).
• Stability: Fixed an issue where the Switch To Window command could incorrectly return an "unknown error" if a web view detached during the command execution; it now correctly ignores the "web view not found" internal error, leading to a standard "no such window" response if the target window indeed closed (crrev.com/c/5583730, Bug: 338616700).
• Stability: Ensured ChromeDriver tolerates target detachment while updating the internal WebView list. If a target detaches during the update, ChromeDriver will now retry instead of returning a non-standard error, reducing flakiness in environments where windows are rapidly created and destroyed (crrev.com/c/5565103, Bug: 338616700, Bug: 4771).
• Navigation: Added logic to ChromeDriver to wait for a navigation detected by the remote end while searching for elements. This prevents ChromeDriver from returning a non-standard error or crashing with a DCHECK when a navigation coincides with an element finding operation (crrev.com/c/5563113, reverting crrev.com/c/5563420, relanding crrev.com/c/5562089, Bug: 4771).
• BiDi: Fixed a race condition between ChromeDriver and BiDiMapper during session creation. ChromeDriver now waits for the browsingContext.getTree command to return a non-empty list before concluding the NewSession command, ensuring the newly created default tab is properly registered (crrev.com/c/5575497, Bug: 341048786, Bug: 1503101).
• BiDi: Fixed an issue where the focus remained in the BiDiMapper background tab after session creation instead of the active user tab by explicitly granting focus to the first user tab (crrev.com/c/5594070, Bug: 341048786, Bug: 1503101).
• BiDi: Stopped ChromeDriver from attempting to attach a Target when handling BiDi commands (like browsingContext.close) to prevent CDP commands from stalling indefinitely if a user prompt is open, delegating the handling entirely to the already-connected BiDi layer (crrev.com/c/5541915, reverting crrev.com/c/5539818, relanding crrev.com/c/5522393, Bug: 4758).
• FedCM: Fixed the fedcm-loginhint.https.html WPT test failure where a dialog was incorrectly marked as closed; the state is now only updated if the selectAccount operation actually succeeds (crrev.com/c/5398379, Bug: 331237776).
• Testing: Fixed a DCHECK failure during JSON parsing when a character hit exactly the kExtendedASCIIStart boundary (crrev.com/c/5565276, Bug: 40284755).
• Testing: Fixed the scrollend-event-fires-to-iframe-window.html WPT test by using the iframe element as the scroll origin and rounding pointer move inputs to whole numbers, preventing ChromeDriver errors with fractional touch positions (crrev.com/c/5570150, Bug: 340956654).
• Testing: Improved diagnostics in ChromeDriver integration tests by printing the attempted paths when run_py_tests.py fails to locate the browser binary (crrev.com/c/5604204, Bug: 4781).

Internal changes and refactors

• BiDi: Bumped the BiDi Mapper dependency, keeping up with the latest protocol updates and bug fixes (crrev.com/c/5614670, crrev.com/c/5593796, crrev.com/c/5537892, crrev.com/c/5471839, Bug: 4226).
• Replaced usages of NOTREACHED() with NOTREACHED_IN_MIGRATION() across the chrome/ directory in preparation for making NOTREACHED() strictly [[noreturn]] (crrev.com/c/5539004, Bug: 40580068).
• Enabled the generation of THIRD_PARTY_NOTICES.txt for ChromeDriver using the licenses.py tool to comply with distribution requirements (crrev.com/c/5596355, Bug: 4777).
• Removed run_wpt_tests.py support for content_shell, as Chromium's WPT coverage is transitioning fully to headless_shell + ChromeDriver (crrev.com/c/5589930). Reorganized wptrunner switches to be embedder-specific to accommodate this change without functional impact (crrev.com/c/5589793, Bug: 338412391).
• Consolidated the logic for JavaScript dialog detection and handling by moving it from JavaScriptDialogManager directly into DevToolsClientImpl, eliminating the separate manager class to simplify testing and reasoning (crrev.com/c/5545630, Bug: 4757).
• Disabled PureBidiTest.testBrowsingContextTreeIsNotEmpty on Mac due to flakiness (crrev.com/c/5588665, Bug: 343891977).
• Updated BiDi WPT expectations to account for recent Mapper updates (crrev.com/c/5615110, Bug: 4226, Bug: 324436866).
• Added unit tests for WebView::SendBidiCommand and BidiTracker to increase code coverage (crrev.com/c/5588400, Bug: 341048786, Bug: 1503101).

ChromeDriver 126

New features

• BiDi: Updated ChromeDriver to supply the --disable-background-timer-throttling switch when launching the browser for a WebDriver BiDi session, preventing background tabs from being throttled (crrev.com/c/5515013, Bug: 4762).
• BiDi: Added support for the BiDi Mapper to send debug messages (sendDebugMessage) when verbose logging is required. ChromeDriver marks these events as bidi messages for parsing, though BidiTracker currently ignores them (crrev.com/c/5465782, Bug: 4753).
• Classic: Implemented auto-acceptance of any beforeunload dialogs (alerts), adhering to the WebDriver standard which dictates they must never be shown in a Classic session (crrev.com/c/5517510, Bug: 4757).

Bug fixes

• Classic: Removed the redundant maximum attempt limitation in the element retrieval logic. Retrieval is now bounded only by the implicit timeout, preventing scenarios where the operation could fail prematurely and incorrectly return a non-standard NoSuchExecutionContext error (crrev.com/c/5478668, Bug: 4379).
• Classic: Fixed a regression that caused ChromeDriver to respond with a javascript error instead of an invalid selector error when a retrieval request used an invalid location strategy (crrev.com/c/5490662, Bug: 4743).
• Classic: Ensured window commands on Android (Maximize, Minimize, Fullscreen) return the standard compliant unsupported operation error instead of proceeding, as these actions are not supported by the Android browser (crrev.com/c/5490224, Bug: 4689).
• Classic: Fixed ChromeDriver to never return the kChromeNotReachable internal error code; it now properly returns the standard kSessionNotCreated error when the HTTP client cannot connect to the browser (crrev.com/c/5476390, Bug: 4379).
• Classic: Fixed ChromeDriver to never return the non-standard kNoSuchExecutionContext error when executing window commands (crrev.com/c/5483606, Bug: 4379).
• Classic: Removed the unused and unsupported kForbidden error code from the list of supported error codes (crrev.com/c/5476927, Bug: 4379).
• BiDi: Updated ChromeDriver to prompt the user before closing the dedicated Mapper tab, aligning with upstream chromium-bidi changes (crrev.com/c/5508600, Bug: 4761).

Internal changes and refactors

• BiDi: Bumped the BiDi Mapper dependency, bringing in the latest features and bug fixes from the upstream chromium-bidi project (crrev.com/c/5490428, crrev.com/c/5471839, crrev.com/c/5509316, crrev.com/c/5458234, Bug: 4226). (Note: A mapper bump was briefly reverted by a gardener and then relanded (crrev.com/c/5374839, crrev.com/c/5374366)).
• Replaced usages of base::StringPiece with std::string_view across //chrome (crrev.com/c/5467746, Bug: 40506050).
• Removed std::to_string() usage in //chrome, replacing it with base::NumberToString() or base::FormatNumber() (crrev.com/c/5505593, Bug: 335672557).
• Removed support for the --remote-debugging-address switch in the old headless mode, as unprotected remote access to the Chrome DevTools Protocol was deemed too dangerous (crrev.com/c/5512634, Bug: 327558594).
• Removed Fuchsia build rules from //chrome, except for ChromeDriver (crrev.com/c/5473870, Bug: 41481724).
• Migrated legacy TODO(crbug.com/...) references across the codebase to the new issue tracker ID format (TODO(b/...)) (crrev.com/c/5492605, crrev.com/c/5486477, crrev.com/c/5461380, Bug: 321899722).
• Disabled WebAuthn (authenticator) tests on Mac (both for headless and chromedriver_py_tests) due to a complex underlying bug, unblocking the upgrade of bots to macOS 14 (crrev.com/c/5525435, crrev.com/c/5518820, Bug: 329130177).
• Disabled WPT builders for content_shell due to difficulties in running WPTs with ChromeDriver and Content Shell together (crrev.com/c/5512439, Bug: 40214293).
• Relanded a change that updates focus-navigation WPTs to use Shift+Tab via test_driver.action_sequence() for backward navigation. Fixed a bug in focus-utils.js where the wrong key code (E050 instead of E008) was used for the Shift key (crrev.com/c/5467843, reverting crrev.com/c/5466531, relanding crrev.com/c/5463903, Bug: 40597271).
• Added crossbench and chromedriver to the perf build targets (crrev.com/c/5521874, Bug: 338627700).

ChromeDriver 125

New features

• Device Posture: Added ChromeDriver commands for device posture management, supporting the Automation section of the Device Posture specification. This allows overriding the hardware-set device posture and removing the override via extension commands (crrev.com/c/5437993, Bug: 330376761).

Bug fixes

• BiDi: Changed the intermediate storage of the incoming BiDi command id from a Double to base::Value. This ensures the id is echoed back precisely in the response without an unexpected trailing decimal point or fractional part after JSON serialization (crrev.com/c/5444225, Bug: 4676).
• FedCM: Relanded the change to enable CORS in the ID assertion endpoint after IDPs were ready (crrev.com/c/5440132, reverting crrev.com/c/5381316, relanding crrev.com/c/5370086, Bug: 40284123).
• FedCM: Fixed a bug where a dialog was improperly marked as closed by ensuring it is only marked as closed if the selectAccount command succeeds. This resolves test failures when selectAccount is called without an expected account chooser (crrev.com/c/5398379, Bug: 331237776). Avoided calling fedcm_get_and_select_first_account when an account chooser is not expected to prevent triggering this bug (crrev.com/c/5398800).
• Testing: Fixed a failure in the popover-light-dismiss.html WPT test by combining action sequences and using the main frame's document as the origin for the pointerUp action, preventing ChromeDriver from incorrectly sending concurrent pointerUp events across frames (crrev.com/c/5402096, Bug: 325981758).
• Testing: Fixed wptrunner to correctly forward stderr output (including browser logs written when using --enable-chrome-logs) to the stderr artifact instead of crash_log, and moved harness errors (which contain the browser stack trace) to crash_log (crrev.com/c/5437023, Bug: 41494889).
• Testing: Fixed wptrunner to route browser logs to the correct test artifact by grouping output by the ChromeDriver process, preventing interleaved and orphaned logs during parallel test execution (crrev.com/c/5320681, Bug: 41494889).

Internal changes and refactors

• BiDi: Bumped the BiDi Mapper dependency, integrating the latest protocol enhancements and bug fixes (crrev.com/c/5433300, crrev.com/c/5393442, Bug: 4226). (Note: A previous bump crrev.com/c/5374366 was reverted crrev.com/c/5374839 and subsequently relanded with disabled flaky tests and updated licenses crrev.com/c/5374914).
• Diagnostics: Plumbed Chrome's StackTrace into ChromeDriver exceptions. This surfaces the browser stack trace in the error message when a session is deleted because of a page/tab crash (e.g., dangling pointers on Mac), significantly improving debuggability (crrev.com/c/5374371, Bug: 330009945).
• Testing: Temporarily disabled the flaky testTakeLargeElementViewportScreenshot integration test on Mac (specifically mac-arm64) (crrev.com/c/5447515, Bug: 333826980).
• Testing: Updated the ChromeDriver launch arguments in testing environments (CEL) to match Selenium 4+ syntax (crrev.com/c/5448812, Bug: 308885357).
• Testing: Extracted the exact chrome command line used to run each WPT test from the chromedriver log into a ResultDB artifact named command. This facilitates manual debugging with run_blink_wptserve.py (crrev.com/c/5441189, Bug: 41494889).
• Dependencies: Removed Closure from the selenium-atoms dependency list, consequently removing it from ChromeDriver's third-party notices (crrev.com/c/5424804, Bug: 4226).
• Dependencies: Dropped unused dependencies on dynamic_annotations across the base repository (crrev.com/c/3398908, Bug: 1282422).
• Formatting: Applied the new clang-format configuration to problematic Windows headers (crrev.com/c/5367127, Bug: 329138753).

ChromeDriver 124

New features

• BiDi: Added a build step to minify the BiDiMapper script before embedding it into ChromeDriver, as the source mapper is now downloaded unminified from CIPD (crrev.com/c/5310075, Bug: 4226).
• WebAuthn: Added the SetCredentialProperties command, allowing clients to update the backup flags for a WebAuthn credential (crrev.com/c/5296389, Bug: 40945430).
• WebAuthn: Exposed WebAuthn backup flags through WebDriver by adding defaultBackupEligibility and defaultBackupState to the "Add Virtual Authenticator" command, and backupEligibility and backupState to the "Add Credential" command (crrev.com/c/5297117, Bug: 40945430).
• Testing: Added support for the --failfast command-line argument to ChromeDriver Python integration tests, stopping the test run on the first error to assist with debugging (crrev.com/c/5374546).
• Testing: Added content-shell support for the SetRPHRegistrationMode webdriver command via testdriver-vendor.js APIs (crrev.com/c/5205730, Bug: 1359103).

Bug fixes

• Stability: Moved the timeout expiration check inside the poll-and-wait loop body in ChromeImpl::SetWindowBounds. This fixes an issue where, under high load, the timeout could expire before the first loop iteration occurred (crrev.com/c/5366899, Bug: 4642).
• Performance: Minimized wait time in ChromeImpl::SetWindowBounds by only applying an exponential backoff wait if the window bounds have not yet reached the desired state, reducing WPT setup latency (crrev.com/c/5366457, Bug: 4642).
• Startup: Updated ChromeDriver to use --user-data-dir instead of --data-path when specifying the data directory for content_shell, aligning with how it reads the active DevTools port (crrev.com/c/5226609, Bug: 1295373).

Internal changes and refactors

• BiDi: Bumped the BiDi Mapper dependency, capturing the latest protocol fixes and features (crrev.com/c/5374366, crrev.com/c/5349491, crrev.com/c/5317650, Bug: 4226). (Note: A bump was briefly reverted and then relanded due to test failures crrev.com/c/5374839, crrev.com/c/5368680, crrev.com/c/5319423).
• Replaced usages of absl::optional with std::optional across the codebase following the transition of absl::optional to a type alias (crrev.com/c/5296147, Bug: 1500249).
• Extended MiraclePtr (raw_ptr) coverage to additional standard containers including std::list, std::unordered_set, base::flat_set, std::stack, and std::queue (crrev.com/c/5306923, Bug: 325302189).
• Converted WriteBigEndian() to use base::numerics byte conversions or BigEndianWriter (which now accepts base::span), improving safety when writing big-endian bytes (crrev.com/c/5202348, Bug: 1490484).
• Switched to using ChromeDriver to run Web Platform Tests (WPT) with content_shell (excluding virtual tests and reftests pending upstream bug fixes) (crrev.com/c/5347371, Bug: 40214293).
• Converted all existing Generic Sensor web tests to use test_driver.js and virtual sensors instead of JS/Mojo mocks, aligning with the new Automation section of the Generic Sensor spec (crrev.com/c/4770867, Bug: 1278377, Bug: 1471996).
• Improved license generation by adding append_notices.py to generate credits for BiDiMapper dependencies and updating the licenses.py invocation to rely strictly on the selenium-atoms README for third-party notices (crrev.com/c/5350601, crrev.com/c/5339957, Bug: 4729, Bug: 4735).

ChromeDriver 123

New features

• FedCM: Show modal dialogs for single account button flows, including adding support for modal views in the automation interface (crrev.com/c/5231438, Bug: 1518356).
• FedCM: Implemented ChromeDriver support for opening links within FedCM dialogs, treating them as buttons for automation simplicity (crrev.com/c/5225543, Bug: 1513520).
• Sensors: Modified WebDriver virtual sensor commands to read Euler angles (alpha-beta-gamma) instead of quaternions, complying with recent orientation-sensor spec updates. Internal CDP and services layers still use quaternions via a conversion step (crrev.com/c/5229177, Bug: 1506995, Bug: 1520912, Bug: 1520919).

Bug fixes

• Classic: Fixed an issue where returning a node from a different frame via a script incorrectly resulted in a StaleElementReference error; it now correctly returns a JavaScriptError to comply with the WebDriver standard (crrev.com/c/5222746, Bug: 4668).
• Testing: Fixed an overscroll events test that was failing on Chrome/ChromeDriver because the touch drag was extending outside the window boundaries; the drag is now properly constrained (crrev.com/c/5297676, Bug: 40832230).
• Testing: Fixed open-close.https.html MIDI tests to not construct promises unnecessarily, avoiding unhandled promise rejections that caused ChromeDriver to fail the test (crrev.com/c/5239869, Bug: 1499775).
• Testing: Corrected the permission set in wpt_internal/system-wake-lock/idlharness* tests where test_driver.set_permission(...) was incorrectly passing false instead of null or a WindowProxy, confusing ChromeDriver (crrev.com/c/5271087, Bug: 40287920).

Internal changes and refactors

• BiDi: Bumped the BiDi Mapper dependency, fetching the latest fixes and features (crrev.com/c/5205452, crrev.com/c/5255321, crrev.com/c/5238148, crrev.com/c/5237125, Bug: 4226). (Note: A bump was briefly reverted and then reapplied due to build failures crrev.com/c/5238855).
• Improved ChromeDriver code health by eliminating unsafe static casts from a base class to a derived class in both ChromeImpl and DevToolsClientImpl, preventing potential undefined behavior (crrev.com/c/5277062, crrev.com/c/5272562, Bug: 4702).
• Eliminated unsafe casts in WebViewImpl (crrev.com/c/5272230, Bug: 4702).
• Removed deprecated forms of base::Base64Encode(), migrating to the newer std::string returning variant instead of using out parameters (crrev.com/c/5179900, crrev.com/c/5246585, Bug: 1486214).
• Updated all #include directives for base/... to use "" instead of <> for consistency (crrev.com/c/5237376, Bug: 1500249).
• Migrated all DIR_METADATA files in chrome/test/ to Buganizer (crrev.com/c/5284119, Bug: 1518875).
• Prevented wptrunner from creating a local - file when passing -vvv by removing the unnecessary chromedriver --log-path=- switch, as stderr is already redirected to stdout (crrev.com/c/5282721).
• Enhanced wptrunner to summarize test results when regressions occur, explicitly including subtest results and ChromeDriver stack traces directly in the summary output (crrev.com/c/5238662, Bug: 1521922).
• Simplified debugging of ChromeDriver integration tests by introducing the --remote-chromedriver-port parameter to run_py_tests.py, allowing connection to an existing instance running under a debugger (crrev.com/c/5237254, Bug: 4693).
• Avoided two-arg base::HexEncode() and RandBytes() calls to let the compiler deduce the correct size, simplifying code (crrev.com/c/5241357).

ChromeDriver 122

Bug fixes

• BiDi: Updated deep node serialization to include loaderId, allowing ChromeDriver and the BiDi Mapper to properly reference and dereference nodes without excessive round trips (crrev.com/c/5116240, Bug: 1420968).
• Capabilities: Updated ChromeDriver to pass the acceptInsecureCerts capability to the BiDi Mapper immediately on start, preventing race conditions where the capability might be applied too late (crrev.com/c/5125711, Bug: 4643).
• Classic: Re-architected element reference generation to use a <frame_id>.<loader_id>.<backend_node_id> format; this allows ChromeDriver to definitively distinguish between valid, unknown, and stale element references across frame navigations and DOM updates (crrev.com/c/5094519, Bug: 4379).
• Classic: Fixed an issue where the window/handles command could fail with a "no such window" error if a newly created target closed itself (e.g., in a race condition) before ChromeDriver could attach to it (crrev.com/c/5147409, Bug: 1506833).
• FedCM: Added an internal event listener to notify when a FedCM dialog is closed, preventing the dialogtype command from returning stale data if the dialog was closed externally (e.g., via AbortController.abort) (crrev.com/c/5067504, Bug: 1506292).
• FedCM: Removed the vendor prefix from the ClickDialogButton command as it has now been approved in the FedCM specification (crrev.com/c/5092527, Bug: 1499341).

Internal changes and refactors

• BiDi: Bumped the BiDi Mapper dependency to the latest version (crrev.com/c/5205452, Bug: 4226).
• Reduced ChromeDriver and Chrome DevTools Protocol (CDP) traffic by removing redundant Page.enable calls sent from every DevToolsEventListener, as DevToolsClientImpl already handles this per target (crrev.com/c/5088789, Bug: 4600).
• Changed all Wptrunner builders for content_shell to experimental status since running tests in protocol mode is currently not fully supported while ChromeDriver integration is in progress (crrev.com/c/5225148, Bug: 1474702).
• Skipped tests that require window.test_driver_internal.get_computed_role on content_shell as it is not yet implemented, preventing TypeError failures (crrev.com/c/5189678, Bug: 1517744).
• Relanded the refactor to use platform-independent IS_OZONE_{X11, WAYLAND} flags instead of OZONE_PLATFORM_* (crrev.com/c/5086329, Bug: 1500494).
• Bumped the selenium-atoms dependency to the latest revision (crrev.com/c/5110808, Bug: 4662).
• Fixed logic in SnapEvents tests when run against the full Chrome binary by rounding pointer move inputs, enforcing the origin parameter for scrolls, and using approximation assertions (assert_approx_equals) to handle fractional scroll/offset discrepancies (crrev.com/c/5097343).
• Added StringPrintfNonConstexpr() helper to distinguish from StringPrintf() when format strings are not compile-time constants (crrev.com/c/4950568, Bug: 1371963).
• Ensured chromium::import! rust macro escaping uses an injective function to prevent collisions in generated GN target names (crrev.com/c/5132119, Bug: 1512174).
• Cleaned up the ScopedTempDirWithRetry implementation by adding a constructor and early returns in the destructor (crrev.com/c/5113843).

ChromeDriver 121

New features

• Testing: Added support for running ChromeDriver integrated tests (chromedriver_py_test) against chrome-headless-shell in addition to the standard Chrome browser on build bots. This includes the ability to discover the browser binary based on the --browser-name parameter and conditionally run specific test sets (crrev.com/c/4995189, crrev.com/c/4989442, Bug: 4358).

Bug fixes

• Stability: Initialized the default KeyboardLayoutEngine as StubKeyboardLayoutEngine to prevent ChromeDriver crashes caused by a DCHECK hit in KeyboardLayoutEngineManager::SetKeyboardLayoutEngine (crrev.com/c/5017859, Bug: 4625).
• Stability: Fixed a flakiness issue where ChromeDriver could crash if the session thread requested to close a connection after the client had already requested to close the same connection (crrev.com/c/4994636, Bug: 4606).
• Resource Management: Fixed resource leaks in ChromeDriver integration tests (RemoteBrowserTest) by ensuring the browser process is terminated even if an exception is thrown by a ChromeDriver command (crrev.com/c/5009554, Bug: 4614).
• Resource Management: Implemented logic in ChromeDriver integration tests to detect and terminate any browser processes abandoned by the ChromeDriver process (crrev.com/c/5014093, Bug: 4617).
• Startup: Fixed an issue where chrome-headless-shell would return an empty target list, preventing session creation, by appending the data:, argument to the browser command line when the browser name is chrome-headless-shell (crrev.com/c/5010392, crrev.com/c/5009535, Bug: 4615, Bug: 4358).
• FedCM: Added a new event to notify when a FedCM dialog is closed, ensuring dialogtype and other commands don't return stale data if the dialog was closed externally (e.g., via AbortController.abort) (crrev.com/c/5067504, Bug: 1506292).
• Testing: Fixed and re-enabled all ChromeDriver integration tests that were previously disabled for chrome-headless-shell on Windows (crrev.com/c/5027594, Bug: 4358).
• Testing: Weakened overly strict assertions in testElementRegionTest to align with the WebDriver standard, resolving flakiness caused by browser rendering peculiarities (crrev.com/c/5017865, Bug: 4526).

Internal changes and refactors

• BiDi: Updated the BiDi Mapper dependency (crrev.com/c/4994305, Bug: 4226).
• Reverted the use of IS_OZONE_{X11, WAYLAND} in favor of OZONE_PLATFORM_* due to a bug (crrev.com/c/5086571, reverting crrev.com/c/5083096, Bug: 1500494).
• Migrated code in commands_unittest.cc to use base::BindLambdaForTesting instead of the deprecated base::Passed (crrev.com/c/5078589, Bug: 1326449).
• Refactored session.new to extract boilerplate capability handling (e.g., testName, binary, browserName) into a dedicated method and ensured the command respects capabilities similarly to the classic command (crrev.com/c/5004665, crrev.com/c/5001510, Bug: 4358, Bug: 4610).
• Removed usage of the deprecated base/strings/string_piece_forward.h header (crrev.com/c/5008994, Bug: 691162).
• Prepared for the transition of net::IOBuffer to a non-owning class by using net::IOBufferWithSize for owning cases (crrev.com/c/4996470, Bug: 1493389).
• Introduced and utilized base::RandBytesAsVector() to avoid storing binary values in strings (crrev.com/c/5018451).
• Disabled several consistently failing Python integration tests on Mac to prevent them from causing green builds due to LUCI analysis exoneration (crrev.com/c/4998771, Bug: 1486604, Bug: 1486520, Bug: 1486474, Bug: 1481915).
• Renamed the webdriver_tests_suite (and wpt_tests_suite) to chrome_wpt_tests to standardize WPT suite naming conventions on Linux try builders (crrev.com/c/5014293, Bug: 1474702).
• Repurposed the ConfirmIdpLogin FedCM webdriver command into a more extensible ClickDialogButton command that accepts a DialogButton parameter (crrev.com/c/5003255, Bug: 1499341).
• Updated the crossbench dependency with numerous fixes and features, including better driver type parsing, network stubs, and iOS support (crrev.com/c/5009937).
• Added missing #include <string> to chrome_finder.h for IWYU compliance (crrev.com/c/4994605, Bug: 957519).

ChromeDriver 120

New features

• BiDi: Added support for session.new and session.end commands, allowing users to create and terminate sessions directly via BiDi commands (crrev.com/c/4941941, Bug: 4496).
• BiDi: Added support for the session.status PureBiDi command, enabling users to establish a WebSocket connection not bound to any session and retrieve the session status (crrev.com/c/4938596, Bug: 4496). (Relanded after a previous revert in crrev.com/c/4922097)
• BiDi: Bumped the BiDi Mapper dependency and aligned with the new, simplified Mapper running process (crrev.com/c/4952609, Bug: 4226).
• Sensors: Implemented virtual sensor commands in browser_protocol.pdl and the CDP layer (Emulation domain), adding support for the Automation section of the Generic Sensor spec (crrev.com/c/4770864, Bug: 1278377).
• Sensors: Added ChromeDriver extension commands for virtual sensor management, translating WebDriver parameters into the new CDP calls (crrev.com/c/4770866, Bug: 1278377).
• Sensors: Added a content_shell code path for virtual sensors manipulation via testdriver.js, bypassing ChromeDriver entirely for web tests (crrev.com/c/4770865, Bug: 1278377).
• Tracking Mitigations: Added ChromeDriver support for Bounce Tracking Mitigations (DIPS), enabling automation of the nav-tracking-mitigations spec (crrev.com/c/4873672, Bug: 1474656). (Note: This was temporarily reverted due to test failures on Mac in crrev.com/c/4938394)

Bug fixes

• Startup: Added Headless Shell discovery to ChromeDriver, allowing it to search for the chrome-headless-shell binary if requested via capabilities and no explicit path is provided (crrev.com/c/4987262, Bug: 4358). (Relanded after a previous revert in crrev.com/c/4984449)
• WebSockets: Implemented partial support for the WebSocket Closing Handshake, ensuring ChromeDriver responds with a CLOSE frame when one is received from the remote end (crrev.com/c/4931500, Bug: 4499).
• Permissions: Exposed options.disclaim_responsibility as a build flag to allow vendor builds (like Microsoft Teams) to turn it off, preventing macOS permission prompts from stalling test automation (crrev.com/c/4929495, Bug: 1223643).
• C++ standard compliance: Fixed undefined behavior (UB) caught by UBSan when casting an out-of-range double to an int by adding range checks (crrev.com/c/4980055, Bug: 1394755).
• FedCM: Removed support for the old header syntax, ensuring compliance with the standard login-status-http syntax (crrev.com/c/4957073, Bug: 1381501).

Internal changes and refactors

• Added testReturnFrameElement integration test to verify ChromeDriver's behavior regarding treating window.frameElement as a stale reference (crrev.com/c/4983549, Bug: 4477).
• Improved logging by ensuring ChromeDriver logs the specific paths where it attempts to locate the browser binary (crrev.com/c/4976116, Bug: 4539).
• Renamed various base::Time functions to be more descriptive (e.g., FromDoubleT() to FromSecondsSinceUnixEpoch()) (crrev.com/c/4956111).
• Refactored net::StringIOBuffer constructor and IOBuffer instantiations to avoid unnecessary string copies and zero-length allocations (crrev.com/c/4938384, crrev.com/c/4959174).
• Cleaned up string handling by replacing base::StrCat with + where applicable and utilizing base::AppendHexEncodedByte() (crrev.com/c/4963465, crrev.com/c/4977165).
• Renamed DIR_SOURCE_ROOT to DIR_SRC_TEST_DATA_ROOT across //chrome* tests for clarity (crrev.com/c/4916045, Bug: 1264897).
• Disabled flaky PureBidiTest tests on Mac builders (crrev.com/c/4983555, Bug: 1496826).

ChromeDriver 119

New features

• BiDi: Implemented support for resolving weak local object references returned by the remote end during remote function calls (crrev.com/c/4886760, Bug: 4536).
• FedCM: Added the vendor-prefixed confirmidpsignin command to support the IDP Sign-In Status API origin trial (crrev.com/c/4811725, Bug: 1451884).

Bug fixes

• Mobile emulation: Fixed an issue where predefined devices without Client Hints (e.g., older configurations) were broken by populating them with sensible default values (crrev.com/c/4887254, Bug: 4550).
• Classic: Fixed serialization of Map and Set objects; they are now correctly serialized as Object rather than Collection since they lack a length property (crrev.com/c/4881378, Bug: 4031).
• Classic: Reinstated the logic to always download and use the latest compatible version of ChromeDriver during tests, falling back to specific versions only when compatibility issues arise (crrev.com/c/4779613, reverting crrev.com/c/4778973).
• FedCM: Standardized the browser automation commands by renaming Signin to Login (confirmidplogin) to align with the latest FedCM specification discussions (crrev.com/c/4901302, Bug: 1451884).
• Testing: Fixed FedCM tests that failed when third-party cookies were disabled by explicitly enabling the IDP Sign-In Status API during test execution (crrev.com/c/4889802, Bug: 1484833).
• Testing: Replaced the invalid URL placeholder ~NOTFOUND with ^NOTFOUND in test runners to comply with upcoming Chromium URL standard enforcement changes (crrev.com/c/4845589, Bug: 1416013).

Internal changes and refactors

• BiDi: Updated the BiDi Mapper dependency to version 0.4.27, bringing in the latest fixes and features (crrev.com/c/4862031, crrev.com/c/4890322).
• Replaced multiple pointer/length APIs in //url with std::string_view for improved safety and convenience (crrev.com/c/4897456).
• Transitioned the generateWebDriverValue utility to use the deep serialization option (serializationOptions.serialization: deep) natively provided by the BiDi protocol (crrev.com/c/4889644).
• Added integration tests to verify that searching under a stale element reference correctly returns a "stale element reference" error (crrev.com/c/4886793, Bug: 4440).
• Improved code style formatting in call_function.js (crrev.com/c/4882511, Bug: 4031).
• Enhanced user feedback by explicitly informing users when they connect via WebSockets that pipes are supported and recommended for better reliability and security (crrev.com/c/4882626, Bug: 3480).
• Updated WPT suite configuration to archive results.html for webdriver_tests_suite tests, providing a better UI for viewing results (crrev.com/c/4873223).
• Fixed DevTools integration with WebView by marking WebView WebContents and setting their DevTools type to popup_page instead of other (crrev.com/c/4842093).
• Renamed the WPT build target chrome_wpt to chrome_wpt_tests for consistency and removed the redundant webdriver_wpt_tests target (crrev.com/c/4847474, Bug: 1474702).
• Migrated run_py_tests.py from the deprecated optparse library to argparse (crrev.com/c/4849411, Bug: 4557).

ChromeDriver 118

New features

• Integration Testing: Introduced C++ integration tests for ChromeDriver, allowing testing of specific classes against real CDP traffic, filling the gap between unit tests and Python integration tests (crrev.com/c/4707855, Bug: 4528).
• Crossbench: Updated the crossbench dependency with numerous improvements including new power benchmark stories, better platform and device support, enhanced debugging, and various fixes (crrev.com/c/4803743).

Bug fixes

• Capabilities: Fixed an issue where debuggerAddress was missing from returned capabilities in default configurations; it is now correctly returned to support Selenium's CDP-based BiDi communication (crrev.com/c/4789068, Bug: 4533).
• Capabilities: Ensured ChromeDriver returns standard platformName values (e.g., 'linux', 'windows', 'mac') as required by the WebDriver specification (crrev.com/c/4797735, Bug: 4548).

Internal changes and refactors

• Migrated code in MockSocket to prefer base::span<> over raw pointers for improved safety (crrev.com/c/4832086).
• Removed deprecated uses of base::raw_ptr and base::raw_ref in favor of their unqualified forms raw_ptr and raw_ref via automated cleanup (crrev.com/c/4773481).
• Temporarily reverted a change that always used the latest ChromeDriver, as it caused crashes on Windows stable/beta channels (crrev.com/c/4778973, reverting crrev.com/c/4777430).
• Adjusted WPT (Web Platform Tests) configurations, including suppressing debug-only failures in pointer_touch.py and implementing browser-side focus verification for fenced frames (crrev.com/c/4844810, crrev.com/c/4572517).
• Added missing #include <vector> to client_hints.h for IWYU compliance (crrev.com/c/4767547).
• Migrated Apple-specific base types (ScopedTypeRef, ScopedCFTypeRef, scoped_nsautorelease_pool) into the base::apple:: namespace, leaving temporary forwarding headers for Crashpad (crrev.com/c/4799213, crrev.com/c/4790744, crrev.com/c/4790741, crrev.com/c/4784010).

ChromeDriver 117

New features

• Pipes Communication: Changed the default communication mode between ChromeDriver and Chrome from WebSockets to pipes (--remote-debugging-in-pipe and --remote-debugging-out-pipe) across all supported platforms, including Windows (crrev.com/c/4634299, crrev.com/c/4628834, crrev.com/c/4635378, Bug: 3480).
• BiDi: Updated the BiDi Mapper dependency (crrev.com/c/4670516, Bug: 4226).

Bug fixes

• Stability: Fixed a null pointer access that caused ChromeDriver to crash, which in turn resulted in ConnectionRefused errors during test runs (crrev.com/c/4675633, Bug: 1457101).
• Navigation: Fixed an issue where Chrome's NoSuchExecutionContext and NoSuchWindow errors during navigation were not handled uniformly; both are now properly mapped to retry the operation (crrev.com/c/4667156, Bug: 4459).
• Mobile emulation: Corrected the inference logic for clientHints.mobile; it is now correctly inferred from the userAgent on Android and defaults to false on other platforms, fixing an issue where tablets incorrectly reported as mobile (crrev.com/c/4649348, Bug: 4243).
• Session creation: Updated session creation to correctly return the standard SessionNotCreated error code upon failure, strictly complying with the W3C WebDriver specification (crrev.com/c/4638223, Bug: 4379). Note: This change was subsequently reverted as some specific code paths require different error codes (crrev.com/c/4651188).

Internal changes and refactors

• Eliminated the manual ChromeDriver release process scripts, as ChromeDriver is now fully integrated into the Chrome release process and available via the Chrome for Testing infrastructure (crrev.com/c/4520687, Bug: 4142).
• Migrated WPT (Web Platform Tests) infrastructure to use the official wptrunner harness instead of the bespoke run_webdriver_tests.py, significantly improving execution speed and reliability, and ensuring ChromeDriver respawns between tests to isolate crashes (crrev.com/c/4723147, crrev.com/c/4676070, crrev.com/c/4639168).
• Extensively refactored ChromeLauncher and related classes to support the transition to pipes, loosening coupling with DevToolsHttpClient and moving WebSocket logic into dedicated branches (crrev.com/c/4632801, crrev.com/c/4674345).
• Renamed the misleading BrowserInfo.is_headless field to BrowserInfo.is_headless_shell for clarity (crrev.com/c/4650452, Bug: 4358).
• Replaced various deprecated base::Value methods with the modern base::Value::Dict equivalents (e.g., FindDouble(), Set(), size()) across the codebase (crrev.com/c/4258936, crrev.com/c/4336805, crrev.com/c/4461067).^{112.0.5603.0, 113.0.5653.0, 114.0.5733.0}
• Removed the use of [w]ctype.h in favor of safer base string utilities and implemented new facilities for base::expected (crrev.com/c/4749459, crrev.com/c/4755226).
• Implemented get_fedcm_dialog_title and select_fedcm_account automation commands in TestDriver for FedCM WPTs (crrev.com/c/4618303).
• Updated BiDi mapper build scripts to function correctly regardless of the current working directory (crrev.com/c/4670550).
• Converted /chrome/test/chromedriver files to use ARC (Automatic Reference Counting) in macOS builds, adding necessary boilerplate (crrev.com/c/4663602).
• Attempted to disable pipe communication by default via an automated rubber-stamper commit, but the change only touched configuration without altering the core pipes-by-default behavior introduced earlier (crrev.com/c/4683947).

ChromeDriver 116

New features

• FedCM: Added a new capability allowing clients to check if ChromeDriver supports FedCM commands without needing to execute them and catch errors (crrev.com/c/4624924, Bug: 1356159).
• Testing: Enabled test window reuse for testharness tests run via ChromeDriver in wptrunner to evaluate its impact on performance and flakiness (crrev.com/c/4515180, Bug: 1394572).

Bug fixes

• C++ standard compliance: Fixed undefined behavior caused by incorrectly using scoped enumerations (enum class) directly in format strings, addressing new Clang compiler warnings (crrev.com/c/4628112, Bug: 1456289).
• FedCM: Addressed a potential cause of test flakiness by fixing an edge case that prevented setdelayenabled from working correctly (crrev.com/c/4606064, Bug: 1453412).

Internal changes and refactors

• BiDi: Bumped the BiDi Mapper dependency and updated the build script to pull the latest revision from 'main' by default (crrev.com/c/4615087, crrev.com/c/4615791, Bug: 4226).
• Transitioned ChromeDriver to open and write all files using UTF-8 encoding explicitly (crrev.com/c/4614522).
• Refactored ChromeImpl to eliminate its dependency on DevToolsHttpClient and reduced the usage of SyncWebSocketFactory and BrowserInfo in preparation for communicating over pipes instead of WebSockets (crrev.com/c/4571690, crrev.com/c/4571199, Bug: 3480).
• Removed the deprecated "default mode" for fenced frames and updated associated tests to enable the new feature flag, continuing the migration to FLEDGE auctions (crrev.com/c/4558645).
• Improved FedCM tests by replacing generic WaitForCondition assertions with assertTrue to clearly indicate when timeouts occur (crrev.com/c/4590211).
• Marked known flaky dangling raw_ptr warnings in linux-rel unittests (crrev.com/c/4598070).
• Updated OWNERS file for the BiDi mapper (crrev.com/c/4614518).

ChromeDriver 115

New features

• Mobile emulation: Implemented support for User-Agent Client Hints in mobile emulation, allowing ChromeDriver to parse client hints from capabilities and presets and pass them to Chrome (crrev.com/c/4498667, crrev.com/c/4466129, Bug: 4243).
• Mobile emulation: Updated mobile emulation presets to use the major version of the host browser instead of the ChromeDriver version when replacing the %s format string in the user agent (crrev.com/c/4502850, Bug: 4243).
• Setup: Added support for downloading a specific ChromeDriver version for a given channel, improving automation scenarios where ChromeDriver runs on a different platform (like Android/WebView) than the host (crrev.com/c/4550281).^116.0.5791.0

Bug fixes

• Classic: Fixed an issue where failing to resolve a node would incorrectly return an UnknownError instead of the standard NoSuchElement error (crrev.com/c/4508952, Bug: 4440).
• Mobile emulation: Added stricter assertions to mobile emulation presets to enforce that the clientHints.mobile flag must be true if the userAgent string contains 'Mobile' (crrev.com/c/4507142, Bug: 4243).
• Mobile emulation: Migrated DeviceMetrics overrides to use the Emulation.setDeviceMetricsOverride CDP command instead of the deprecated Page domain equivalent (crrev.com/c/4502614, Bug: 4243).

Internal changes and refactors

• BiDi: Updated the BiDi Mapper dependency, enabling deep serialization features (crrev.com/c/4535936, crrev.com/c/4512195).
• Removed the deprecated Connect method from DevToolsClient in preparation for migrating ChromeDriver to communicate over pipes (crrev.com/c/4521485, Bug: 3480).
• Migrated the codebase to prefer base::Value::Dict over base::Value and replaced deprecated methods like FindStringKey(), SetKey(), and SetByDottedPath() (crrev.com/c/4529788, crrev.com/c/4522701, crrev.com/c/4515800, crrev.com/c/4507150).
• Switched to using string_util.h functions in place of [w]ctype.h for safer type conversions (crrev.com/c/4529187).
• Changed the seed file loading logic to use absolute paths to ensure consistency when scripts and Chrome run in different locations (crrev.com/c/4504656).
• Removed the unused CallAsyncFunction() method from web_view.h (crrev.com/c/4518363, Bug: 3376).
• Applied an automated rename of base::raw_ptr to raw_ptr to follow style guide preferences (crrev.com/c/4476651).

ChromeDriver 114

New features

• Classic: Passed MobileDevice information to MobileEmulationOverrideManager to lay the groundwork for future Client Hints and UserAgent overrides (crrev.com/c/4447524).
• Testing: Added test fixtures for ChromeDriver (crrev.com/c/4459939).

Bug fixes

• Headless: Fixed a crash in the new headless mode by quietly ignoring scripted print preview requests (e.g., window.print()), aligning behavior with the old headless mode (crrev.com/c/4436313, Bug: 4385).
• Capabilities: Fixed a use-after-move bug in ChromeDriver capabilities (crrev.com/c/4462094, Bug: 4243).
• DevTools: Removed a DCHECK in DevToolsClientImpl::SendCommandInternal to prevent crashes when the DevTools connection breaks, as this is not an invariant violation (crrev.com/c/4370486, Bug: 4385).

Internal changes and refactors

• BiDi: Updated the BiDi Mapper dependency (crrev.com/c/4418727).
• Addressed multiple dangling pointer warnings during unit test execution by properly managing unowned references and local destruction in WebViewImpl and performance logger tests (crrev.com/c/4374824, crrev.com/c/4368179).
• Migrated codebase to use the new base::Value v2 API, replacing deprecated methods like Value::SetPath(), Value::SetStringPath(), and base::ListValue (crrev.com/c/4452309, crrev.com/c/4431420, crrev.com/c/4422897, crrev.com/c/4377520).
• Replaced all uses of base::GUID with base::Uuid to align with the core base library rename (crrev.com/c/4455083).
• Performed miscellaneous code cleanups, including shortening code, using monadic operations for expected, removing dead code, and fixing style violations (crrev.com/c/4475368, crrev.com/c/4464199).
• Updated tests involving fenced frames to use the config attribute instead of the deprecated src attribute (crrev.com/c/4382231).
• Removed ineffective ShadowDOMV0 usage (crrev.com/c/4388302).
• Reverted the addition of a flag for a Skia PDF fix (SK_IGNORE_PDF_EOF_NEWLINE_FIX) to allow rebaselining (crrev.com/c/4401451).
• Updated the owner for the ChromeDriver test script and made adjustments to generate the configuration JSON exclusively for pinpoint (crrev.com/c/4437492, crrev.com/c/4298554).
• Added a missing include (<cstring>) for std::strlen in web_view_impl.cc to fix an IWYU build issue (crrev.com/c/4376772).
• Removed an unused test file (orientation_test.html) (crrev.com/c/4335668).

ChromeDriver 113.0.5672.63

Supports Chrome version 113

• Resolved issue 4205: Same object ids in Classic and BiDi [Pri-1]
• Resolved issue 4302: Don't assume that Mapper is in the first tab in ExecuteGetWindowHandles [Pri-1]
• Resolved issue 4356: Chrome 110 not utilizing pref value "download.default_directory" [Pri-1]

For more details, see the release notes.

ChromeDriver 113.0.5672.24

Supports Chrome version 113

• Resolved issue 4205: Same object ids in Classic and BiDi [Pri-1]
• Resolved issue 4302: Don't assume that Mapper is in the first tab in ExecuteGetWindowHandles [Pri-1]
• Resolved issue 4356: Chrome 110 not utilizing pref value "download.default_directory" [Pri-1]

For more details, see the release notes.

ChromeDriver 112.0.5615.49

Supports Chrome version 112

• Resolved issue 3517: Enable print feature for non-headless [Pri-]
• Resolved issue 4419: Large overhead on Speedometer when using chromedriver [Pri-3]

For more details, see the release notes.

ChromeDriver 112.0.5615.28

Supports Chrome version 112

• Resolved issue 4357: Chromedriver version 110.0.5481.77 session issue with --headless and --user-data-dir options. [Pri-1]

For more details, see the release notes.

ChromeDriver 111.0.5563.64

Supports Chrome version 111

• Resolved issue 4216: Run ChromeDriver with custom BiDiMapper [Pri-]
• Resolved issue 4300: Window handle is interoperable between Classic and BiDi [Pri-]
• Resolved issue 4325: Handling of toJSON in jsonSerialize of call_function.js deviates from the standard. [Pri-]
• Resolved issue 4330: DCHECK fails at DevToolsClientImpl::AddListener [Pri-]
• Resolved issue 4357: ChromeDriver session issue with --headless and --user-data-dir options [Pri-1]

For more details, see the release notes.

ChromeDriver 111.0.5563.41

Supports Chrome version 111

• Resolved issue 4357: ChromeDriver session issue with --headless and --user-data-dir options [Pri-1]

For more details, see the release notes.

ChromeDriver 111.0.5563.19

Supports Chrome version 111

• Resolved issue 4216: Run ChromeDriver with custom BiDiMapper [Pri-]
• Resolved issue 4300: Window handle is interoperable between Classic and BiDi [Pri-]
• Resolved issue 4325: Handling of toJSON in jsonSerialize of call_function.js deviates from the standard. [Pri-]
• Resolved issue 4330: DCHECK fails at DevToolsClientImpl::AddListener [Pri-]

For more details, see the release notes.

ChromeDriver 110.0.5481.77

Supports Chrome version 110

• Resolved issue 4193: Failed to start new session on Android 13 [Pri-]
• Resolved issue 4272: WebSocket should treat code=0 as an indication of FIN [Pri-]
• Resolved issue 4276: Fix connectivity issues in ChromeDriver [Pri-]
• Resolved issue 4295: ChromeDriver with "webSocketUrl": true is racy [Pri-]
• Resolved issue 4297: ChromeDriver Bidi serializes incorrectly [Pri-]

For more details, see the release notes.

ChromeDriver 110.0.5481.30

Supports Chrome version 110

• Resolved issue 4193: Failed to start new session on Android 13 [Pri-]
• Resolved issue 4272: WebSocket should treat code=0 as an indication of FIN [Pri-]
• Resolved issue 4276: Fix connectivity issues in ChromeDriver [Pri-]
• Resolved issue 4295: ChromeDriver with "webSocketUrl": true is racy [Pri-]
• Resolved issue 4297: ChromeDriver Bidi serializes incorrectly [Pri-]

For more details, see the release notes.

ChromeDriver 109.0.5414.74

Supports Chrome version 109

• Resolved issue 4179: BiDi session must support multiple connections [Pri-]
• Resolved issue 4203: Improve credits information [Pri-]
• Resolved issue 4263: Crash on Meta+A [Pri-]

For more details, see the release notes.

ChromeDriver 109.0.5414.25

Supports Chrome version 109

• Resolved issue 4179: BiDi session must support multiple connections [Pri-]
• Resolved issue 4203: Improve credits information [Pri-]
• Resolved issue 4263: Crash on Meta+A [Pri-]

For more details, see the release notes.

ChromeDriver 108.0.5359.71

Supports Chrome version 108 For more details, see the release notes.

ChromeDriver 108.0.5359.22

Supports Chrome version 108

• Resolved issue 4204: Fix the failing WPT test_top_level_and_one_child [Pri-]
• Resolved issue 4215: Rename chromedriver_mac64_m1 build to chromedriver_mac_arm64 [Pri-]
• Resolved issue 4221: Crash when a click command closes the browser [Pri-]

For more details, see the release notes.

ChromeDriver 107.0.5304.62

Supports Chrome version 107

For more details, see the release notes.

ChromeDriver 107.0.5304.18

Supports Chrome version 107

• Resolved issue 4180: Prohibit any BiDi commands handling until notified that BiDiMapper has started [Pri-]
• Resolved issue 4198: ChromeDriver BiDi should not assume that BiDiMapper is always in the first tab [Pri-]
• Resolved issue 4207: WebDriver error when running WPT [Pri-1]

For more details, see the release notes.

ChromeDriver 106.0.5249.61

Supports Chrome version 106

For more details, see the release notes.

ChromeDriver 106.0.5249.21

Supports Chrome version 106

• Resolved issue 4016: Add basic BiDi support to ChromeDriver (Mapper based) [Pri-1]

For more details, see the release notes.

ChromeDriver 105.0.5195.52

Supports Chrome version 105

For more details, see the release notes.

ChromeDriver 105.0.5195.19

Supports Chrome version

For more details, see the release notes.

ChromeDriver 104.0.5112.79

Supports Chrome version 104

For more details, see the release notes.

ChromeDriver 104.0.5112.29

Supports Chrome version 104

• Resolved issue 4121: WebDriver command sometimes fails with "unexpected command response" [Pri-1]

For more details, see the release notes.

ChromeDriver 104.0.5112.20

Supports Chrome version 104

• Resolved issue 4121: WebDriver command sometimes fails with "unexpected command response" [Pri-1]

For more details, see the release notes.

ChromeDriver 103.0.5060.134

Supports Chrome version 103

• Resolved issue 4048: target frame detached [Pri-]
• Resolved issue 4121: WebDriver command sometimes fails with "unexpected command response" [Pri-1]

For more details, see the release notes.

ChromeDriver 103.0.5060.53

Supports Chrome version 103

• Resolved issue 4048: target frame detached [Pri-]

For more details, see the release notes.

ChromeDriver 103.0.5060.24

Supports Chrome version 103

For more details, see the release notes.

ChromeDriver 102.0.5005.61

Supports Chrome version 102

• Resolved issue 1309282: chromedriver doesn't support multivalued switches [Pri-1]

For more details, see the release notes.

ChromeDriver 102.0.5005.27

Supports Chrome version 102

• Resolved issue 1309282: chromedriver doesn't support multivalued switches [Pri-1]

For more details, see the release notes.

ChromeDriver 101.0.4951.41

Supports Chrome version 101

• Resolved issue 4046: DCHECK hit when appending empty fenced frame [Pri-]
• Resolved issue 4080: Switching to nested frame fails [Pri-]

For more details, see the release notes.

ChromeDriver 101.0.4951.15

Supports Chrome version 101

• Resolved issue 4046: DCHECK hit when appending empty fenced frame [Pri-]
• Resolved issue 4080: Switching to nested frame fails [Pri-]

For more details, see the release notes.

ChromeDriver 100.0.4896.60

Supports Chrome version 100

• Resolved issue 4002: Support Fenced Frames [Pri-]

For more details, see the release notes.

ChromeDriver 100.0.4896.20

Supports Chrome version 100

• Resolved issue 4002: Support Fenced Frames [Pri-]

For more details, see the release notes.

ChromeDriver 99.0.4844.51

Supports Chrome version 99

For more details, see the release notes.

ChromeDriver 99.0.4844.35

Supports Chrome version 99

• REVERTED!!! Resolved issue 2269: Impossible to use non-BMP characters (code points above U+FFFF) [Pri-3]
• Resolved issue chromium:1295243: Regression in ChromeDriver sendKeys [Pri-1]

For more details, see the release notes.

ChromeDriver 99.0.4844.17

Supports Chrome version 99

For more details, see the release notes.

ChromeDriver 98.0.4758.102

Supports Chrome version 98

• Resolved issue 3933: Click at edge of viewport is ineffective without error [Pri-]
• REVERTED!!! Resolved issue 2269: Impossible to use non-BMP characters (code points above U+FFFF) [Pri-3]
• Resolved issue chromium:1295243: Regression in ChromeDriver sendKeys [Pri-1]

For more details, see the release notes.

ChromeDriver 98.0.4758.80

Supports Chrome version 98

• Resolved issue 3933: Click at edge of viewport is ineffective without error [Pri-]
• Resolved issue 2269: Impossible to use non-BMP characters (code points above U+FFFF) [Pri-3]

For more details, see the release notes.

ChromeDriver 98.0.4758.48

Supports Chrome version 98

• Resolved issue 3933: Click at edge of viewport is ineffective without error [Pri-]
• Resolved issue 2269: Impossible to use non-BMP characters (code points above U+FFFF) [Pri-3]

For more details, see the release notes.

ChromeDriver 97.0.4692.71

Supports Chrome version 97

• Resolved issue 3878: Better handling of fractional element coordinates for element click [Pri-]

For more details, see the release notes.

ChromeDriver 97.0.4692.36

Supports Chrome version 97

• Resolved issue 3878: Better handling of fractional element coordinates for element click [Pri-]

For more details, see the release notes.

ChromeDriver 97.0.4692.20

Supports Chrome version 97

• Resolved issue 3878: Better handling of fractional element coordinates for element click [Pri-]

For more details, see the release notes.

ChromeDriver 96.0.4664.45

Supports Chrome version 96

• Resolved issue 3445: Impossible to access elements in iframe inside a shadow root [Pri-3]

For more details, see the release notes.

ChromeDriver 96.0.4664.35

Supports Chrome version 96

• Resolved issue 3445: Impossible to access elements in iframe inside a shadow root [Pri-3]

For more details, see the release notes.

ChromeDriver 96.0.4664.18

Supports Chrome version 96

• Resolved issue 3445: Impossible to access elements in iframe inside a shadow root [Pri-3]

For more details, see the release notes.

ChromeDriver 95.0.4638.69

Supports Chrome version 95

• Resolved issue 3857: Host header or origin header is specified and is not whitelisted or localhost [Pri-1]
• Added --allowed-origins argument

For more details, see the release notes.

ChromeDriver 95.0.4638.54

Supports Chrome version 95

• Resolved issue 3857: Host header or origin header is specified and is not whitelisted or localhost [Pri-1]
• Added --allowed-origins argument

For more details, see the release notes.

ChromeDriver 95.0.4638.17

Supports Chrome version 95

• Resolved issue 3857: Host header or origin header is specified and is not whitelisted or localhost [Pri-1]
• Added --allowed-origins argument

For more details, see the release notes.

ChromeDriver 95.0.4638.10

Supports Chrome version 95

• Resolved issue 3857: Host header or origin header is specified and is not whitelisted or localhost [Pri-1]
• Added --allowed-origins argument

For more details, see the release notes.

ChromeDriver 94.0.4606.113

Supports Chrome version 94

For more details, see the release notes.

ChromeDriver 94.0.4606.61

Supports Chrome version 94

For more details, see the release notes.

ChromeDriver 94.0.4606.41

Supports Chrome version 94

For more details, see the release notes.

ChromeDriver 93.0.4577.63

Supports Chrome version 93

For more details, see the release notes.

ChromeDriver 93.0.4577.15

Supports Chrome version 93

For more details, see the release notes.

ChromeDriver 92.0.4515.107

Supports Chrome version 92

For more details, see the release notes.

ChromeDriver 92.0.4515.43

Supports Chrome version 92

• Resolved issue 3389: Host validation for ChromeDriver requests

For more details, see the release notes.

ChromeDriver 91.0.4472.101

Supports Chrome version 91

• Resolved issue 1205107: Unable to get attribute value for fields on the web application.

For more details, see the release notes.

ChromeDriver 91.0.4472.19

Supports Chrome version 91

• Resolved issue 3744: SendKeys() and Click() silently fail after link navigation
• Resolved issue 3746: attribute endpoint incorrectly updates values

For more details, see the release notes.

ChromeDriver 90.0.4430.24

Supports Chrome version 90

• Resolved issue 3708: GetElementLocation's inView fails for elements in shadow DOM
• Resolved issue 3721: Collect performance log for service worker when enabled
• Resolved issue 3731: AdbImpl::GetPidByName doesn't work correctly on non-standard Android OS's like on OnePlus
• Resolved issue 3733: Catastrophic failure with domain on localhost
• Resolved issue 3734: Driver should Error Attempting to set Cookie on Wrong Domain
• Resolved issue 3743: Refactor call function and fix remove element issue

For more details, see the release notes.

ChromeDriver 89.0.4389.23

Supports Chrome version 89

• Resolved issue 3667: Timed out receiving a message from renderer
• Resolved issue 3675: GetElementLocation uses inView method which mishandles boolean as array
• Resolved issue 3682: GetElementRegion returns incorrect size for elements which are partially out of viewport
• Resolved issue 3690: ChromeDriver fails if extensions use chrome.windows API

For more details, see the release notes.

ChromeDriver 88.0.4324.96

Supports Chrome version 88

• Resolved issue 3641: Page not getting loaded/rendered when browser window is not in focus with Chrome Beta v87 and chromedriver v(87/86)

For more details, see the release notes.

ChromeDriver 88.0.4324.27

Supports Chrome version 88

• Resolved issue 3611: getText() output in protractor different from <element>.innerText
• Resolved issue 3625: Improve element screenshot compatibility
• Resolved issue 3628: Stale Element Reference and wrong URL reported back with URL having another URL as part of its path
• Resolved issue 3631: Add support for the webauthn:extension:largeBlob capability
• Resolved issue 3635: Chromedriver 86 - chromedriver.quit() doesn't seem to pass unload event properly
• Resolved issue 3649: Copying selected text to clipboard doesn't work on Windows 10 when using headless mode

For more details, see the release notes.

ChromeDriver 87.0.4280.88

Supports Chrome version 87

• Resolved issue 3641: Page not getting loaded/rendered when browser window is not in focus with Chrome Beta v87 and chromedriver v(87/86)
• Resolved issue 3657: Screenshot background browser timed out

For more details, see the release notes.

ChromeDriver 87.0.4280.20

Supports Chrome version 87

• Resolved issue 2421: Delete old port-forwarding channels on android adb-server
• Resolved issue 3474: Emulated mobile device list needs updating
• Resolved issue 3507: Implement "get computed role"
• Resolved issue 3508: Implement "get computed label"
• Resolved issue 3584: Rename ChromeDriver command line option --whitelisted-ips
• Resolved issue 3588: Bidi WebSocket connection
• Resolved issue 3594: Navigation completes prematurely if OOPIF loads before main page
• Resolved issue 3598: A command line option for devtools port to be forwarded to webview_devtools_remote socket
• Resolved issue 3608: Chromedriver debuggerAddress doesn't support ipv6

For more details, see the release notes.

ChromeDriver 86.0.4240.22

Supports Chrome version 86

• Resolved issue 3370: Shut down Chrome gracefully or cookie will not be correctly saved to SQLite persistence file
• Resolved issue 3401: Get Element Location JS doesn't locate the visible center of the element
• Resolved issue 3462: For sendKeys, CMD key don't work for MAC
• Resolved issue 3541: Improve log between Client and ChromeDriver
• Resolved issue 3559: Output Chrome version when ChromeDriver reports incompatible

For more details, see the release notes.

ChromeDriver 85.0.4183.87

Supports Chrome version 85

• Resolved issue 3578: Chrome 85 no longer allows graceful interaction with windows when an alert dialog is open

For more details, see the release notes.

ChromeDriver 85.0.4183.83

Supports Chrome version 85

• Resolved issue 3577: ChromeDriver 85 doesn't detect changed Chrome directory (C:\Program Files)

For more details, see the release notes.

ChromeDriver 85.0.4183.38

Supports Chrome version 85

• Resolved issue 3214: ChromeDriver78: Sendkeys resets text selection with contenteditable
• Resolved issue 3376: Remove LaunchApp command from ChromeDriver
• Resolved issue 3432: Sometimes NavigationTracker fails to detect when the page has finished loading
• Resolved issue 3481: New Print endpoint according to w3c spec
• Resolved issue 3488: driver.get doesn't throw error when proxy is wrong configured
• Resolved issue 3502: Use document.hasFocus() to check if element is focused
• Resolved issue 3515: selenium.common.exceptions.WebDriverException: Message: unknown error: bad inspector message

For more details, see the release notes.

ChromeDriver 84.0.4147.30

Supports Chrome version 84

• Resolved issue 3420: after switching to the print window, the chromedriver stops responding
• Resolved issue 3421: Driver returns Cyrillic text without styles
• Resolved issue 3422: GetElementText breaks with prototype 1.6.0.3
• Resolved issue 3434: Cannot get 'assert' messages from the 'browser' logs

For more details, see the release notes.

ChromeDriver 83.0.4103.39

Supports Chrome version 83

• Updated Chromedriver to work correctly with prototype.js.

For more details, see the release notes.

ChromeDriver 83.0.4103.14

Supports Chrome version 83

• Resolved issue 1778: Deprecate launchApp from ChromeDriver
• Resolved issue 2520: InitSession can wait forever when Chrome is unresponsive
• Resolved issue 3120: Headless mode download from new tab
• Resolved issue 3234: Confirm semicolon found before substring
• Resolved issue 3240: ExecuteGetElementRect doesn't check returned status from GET_SIZE
• Resolved issue 3331: The get_cookies() method is returning 'expiry' keys of type double, but should be int64 in w3c mode
• Resolved issue 3332: Retry timeout logged as severe
• Resolved issue 3339: Chromedriver exited unexpectedly with code null, signal SIGTRAP
• Resolved issue 3351: Improve Security Considerations message
• Resolved issue 3352: Support SendKeys for color elements
• Resolved issue 3353: Wait for Pending Navigation continues after frame context destroyed
• Resolved issue 3375: Chromedriver v80 stalls on getPageSource on some sites
• Resolved issue 3383: ChromeDriver 80+ on Windows seems to exit or stall on certain element or click commands
• Resolved issue 3399: Remove wasThrown check

ChromeDriver 81.0.4044.138

Supports Chrome version 81

• Updated Chromedriver to work correctly with prototype.js.

For more details, see the release notes.

ChromeDriver 81.0.4044.69

Supports Chrome version 81

• Fixed: Chromedriver crashes on getPageSource on some sites.
  • Fixed: ChromeDriver crashes on certain element or click commands.

For more details, see the release notes.

ChromeDriver 81.0.4044.20

Supports Chrome version 81

• Fixed error when attempting to get location of html element.
  • Get and Add Cookie commands are now frame specific.
  • Resolved some issues that occur with sites that redefine standard Javascript objects.
  • ChromeDriver will continue to wait for loading to complete after receiving a Target Closed message.
  • Chromedriver now returns spec compliant error code for timeouts
  • Fixed: ChromeDriver Unexpected Slow response time on NewSession Command.
  • User-defined timeouts of over 10 minutes are now supported.
  • Fixed: ChromeDriver unable to connect to DevTools due to IPv4 vs IPv6 mismatch.
  • Restored search order for Chrome binary on Linux.

For more details, see the release notes.

ChromeDriver 80.0.3987.106

Supports Chrome version 80

• Restored search order for Chrome binary on Linux

For more details, see the release notes.

ChromeDriver 80.0.3987.16

Supports Chrome version 80

• Fixed Load page was aborted when using a proxy.
• Chromedriver now waits for Current frame to load.
• ChromeDriver log will include the port used by the driver.
• Enabled SetGeoLocation for w3c mode.
• Added missing Alert text for UnexpectedAlertOpen status.
• Improved message when CRX2 Extension is loaded.
• Fixed a potential race condition in ExecuteGetPageSource.
• ChromeDriver will add --ignore-certificate-errors flag when acceptInsecureCerts capability is true
• Updated the error message and return status for no such execution context
• Fixed: ChromeDriver may block indefinitely while waiting for pending navigation.
• Added SameSite attribute to AddCookie and GetCookie.

For more details, see the release notes.

ChromeDriver 79.0.3945.36

Supports Chrome version 79

Includes the following change over version 79.0.3945.16:

• Fixed incorrect calculation of element coordinates

For more details, see the release notes.

ChromeDriver 79.0.3945.16

Supports Chrome version 79

• Fixed ChromeDriver crash caused by javascript alert fired during command execution
  • Fixed a bug causing Chromedriver to lock when an alert is fired while taking a screenshot
  • Removed --ignore-certificate-errors from Chrome launch command
  • Changed platform and platformName to windows on Win10
  • Fixed undefined window.navigator.webdriver when "enable-automation" is excluded
• Fixed WPT test "test_not_editable_inputs[hidden]"
  • Fixed "Element is not clickable" when using headless mode

For more details, see the release notes.

ChromeDriver 78.0.3904.105

Supports Chrome version 78

Includes the following change over version 78.0.3904.70: * Fixed incorrect calculation of element coordinates

For more details, see the release notes.

ChromeDriver 78.0.3904.70

Supports Chrome version 78

Includes the following change over version 78.0.3904.11:

• Reverted the change to adjust screeshot size on retina display, due to multiple issues reported

For more details, see the release notes.

ChromeDriver 78.0.3904.11

Supports Chrome version 78

• Fixed several issues in JavaScript object serialization
  • Fixed a bug in capability matching for Chrome on Android
  • Implemented permissions automation
  • Fixed screenshot size on retina display
• Fixed page load timeout in some scenarios
  • Improved platformName capability matching
  • Fixed error code returned while moving pointer to drop-down list options
  • Fixed an issue affecting download in headless mode

For more details, see the release notes.

ChromeDriver 77.0.3865.40

Supports Chrome version 77

Includes the following changes over version 77.0.3865.10:

• Fixed two bugs in serializing and deserializing JavaScript objects
• Fixed handling of platformName: android while matching capabilities

For more details, see the release notes.

ChromeDriver 77.0.3865.10

Supports Chrome version 77

• Fixed several issues in the implementation of Actions API
  • Improved JavaScript code execution and result handling
  • Fixed a bug that incorrectly rejected POST requests with empty body in OSS mode
• A more robust navigation tracker
• Support eager page load strategy
  • Added New Window command from W3C WebDriver spec
• Support to save file downloads in headless mode
• Added support for loading CRX3 extensions

For more details, see the release notes.

ChromeDriver 76.0.3809.126

Supports Chrome version 76

Includes the following changes over version 76.0.3809.68:

• Fixed two bugs in serializing and deserializing JavaScript objects

For more details, see the release notes.

ChromeDriver 76.0.3809.68

Supports Chrome version 76

Includes the following changes over version 76.0.3809.25:

• Fixed a bug in detecting circular reference in JavaScript objects
• Fixed a bug that causes ChromeDriver to crash when certain types of JavaScript errors occur
• Fixed a bug that prevents actions API to interact with elements inside shadow DOMs
  • Fixed a bug in keeping track of modifier key state between actions API commands
  • Fixed a bug in keeping track of pointer locations between actions API commands
  • Save "Cannot call non W3C standard command while in W3C mode" error to log file when it occurs

For more details, see the release notes.

ChromeDriver 76.0.3809.25

Supports Chrome version 76

Includes the following changes over version 76.0.3809.12:

• Fixed a bug that incorrectly rejected POST requests with empty body in OSS mode
• Added new endpoints for retrieving Chrome log
  • Added endpoint for Is Displayed command in W3C mode

For more details, see the release notes.

ChromeDriver 76.0.3809.12

Supports Chrome version 76

• Finished implementation of Actions API
  • Improved spec compliance of script timeout handling
  • Improved serialization of results from Execute Script command
  • Fixed issues in scrolling element into view
  • Added handling of Cancel key defined in WebDriver spec
  • Fixed processing of unhandled alert error response
  • Fixed processing of <details> element
  • Updated excludeSwitches option to allow optional leading dashes in switch names

For more details, see the release notes.

ChromeDriver 75.0.3770.140

Supports Chrome version 75

Includes the following changes over version 75.0.3770.90:

• Fixed a bug that caused ChromeDriver to crash when some types of JavaScript error occurs
• Fixed a bug in preserving modifier key state between actions

For more details, see the release notes.

ChromeDriver 75.0.3770.90

Supports Chrome version 75

Includes the following changes over version 75.0.3770.8:

• Fixed a bug that incorrectly rejected POST requests with empty body in OSS mode
• Added new endpoints for retrieving Chrome log

For more details, see the release notes.

ChromeDriver 75.0.3770.8

Supports Chrome version 75

The most noticeable change is ChromeDriver now runs in W3C standard compliant mode by default. Other changes include:

• Fixed a bug that caused blur event to be raised twice during element clear
• Renamed capability loggingPrefs to goog:loggingPrefs, as required by W3C standard
• Fixed error handling in W3C mode
  • Correct handling of creating cookies without leading dot in the domain name
  • Allows null for script timeout
  • Fixed Element Send Keys command to file input with 'multiple' attribute
  • Fixed Get Active Element command to return "no such element" error when no active element exists
  • Fixed navigation to malformed URL to return "invalid argument" error
  • Fixed HTTP status code when invalid session id is received
  • Fixed error response when input parameter is missing or malformed
  • Fixed Execute Script command to handle line-oriented JavaScript comment

For more details, see the release notes.

ChromeDriver 74.0.3729.6

Supports Chrome version 74

• Fixed a bug that generated unexpected debug.log file on Windows
• Fixed mouse clicking and drag / drop inside SVG document
• Added cache-control header in responses from ChromeDriver
• Fixed the type of error when click is intercepted by a different element
• Fixed a bug that caused ChromeDriver to fail on Linux devices without /dev/shm
• Fixed some types of double click events
• Fixed Get Sessions command
• Fixed error checking in Switch To Frame command
• Fixed Get Page Source command

For more details, see the release notes.

ChromeDriver 73.0.3683.68

Supports Chrome version 73

• Fixed a bug that generated unexpected debug.log file on Windows
• Fixed error code returned from Execute Script command in some scenarios
• Added cache-control header in responses from ChromeDriver
• Made the HTTP server keep connection alive by default
• Fixed Close Window command to correctly handle user prompts
• Fixed error code returned while sending keys to disabled element
• Improved spec compliance of timeout value handling
• Improved spec compliance of Add Cookie command
  • Increased HTTP server listening queue length
• Fixed Is Element Displayed command in v0 shadow DOM
  • Added warning about Element Clear command behavior change in log file
• Fixed Execute Script command to correctly convert document.all into JSON format
• Improved handling of bad element reference

For more details, see the release notes.

ChromeDriver 2.46

Supports Chrome v71-73

• Fixed error code returned from Execute Script command in some scenarios
• Made the HTTP server keep connection alive by default
• Fixed Close Window command to correctly handle user prompts
• Fixed error code returned while sending keys to disabled element
• Improved spec compliance of timeout value handling
• Improved spec compliance of Add Cookie command
• Improved spec compliance of Switch to Frame command
• Increased HTTP server listening queue length
• Fixed Is Element Displayed command in v0 shadow DOM
• Fixed Element Double Click command
• Added warning about Element Clear command behavior change in log file
• Fixed Execute Script command to correctly convert document.all into JSON format
• Improved handling of bad element reference

For more details, see the release notes.

ChromeDriver 2.45

Supports Chrome v70-72

• Fixed New Session is not spec compliant
• Fixed ChromeDriver shouldn't launch Chrome if Chrome and ChromeDriver versions are incompatible
• Fixed Find Element command returns wrong error code when an invalid locator is used
• Fixed Some ChromeDriver status codes are wrong
• Fixed Compile error in JS inside of WebViewImpl::DispatchTouchEventsForMouseEvents
• Fixed Window size commands should handle user prompts
• Fixed ChromeDriver doesn't start Chrome correctly with Chrome option "user-data-dir="
• Fixed Status command is not spec compliant
• Fixed Add support for strictFileInteractability

ChromeDriver 2.44

Supports Chrome v69-71

• Fixed WindowMaximize on Mac
• Fixed Incorrect 'alert open error' for window handle call
• Fixed Element Send Keys should get "text" property in W3C mode
• Fixed XML special case of Is Element Enabled is not handled as per spec
• Fixed XML special case of Get Element CSS Value is not handled as per spec
• Fixed Set Window Rect needs to check for invalid input
• Fixed Support new unhandledPromptBehavior modes

ChromeDriver 2.43

Supports Chrome v69-71

Changes include:

• Fixed Parsing of proxy configuration is not standard compliant
• Fixed Launch app command is flaky
• Fixed Screenshot of element inside iFrame is taken incorrectly
• Added ChromeDriver supports window resizing over a remote connection
• Fixed Error codes are not handled in Clear element
• Fixed Not waiting until element is visible
• Fixed Get element property is not implemented
• Fixed Switch to Frame is not spec compliant
• Fixed Execute Async Script doesn't return spec compliant error codes
• Fixed Execute Script doesn't return spec compliant error codes
• Fixed Error code in ExecuteGet is not conformant with spec
• Fixed Send Alert Text is not returning spec compliant error codes
• Fixed clear() on an input type="date" pretends element is not user-editable
• Fixed Chromedriver gets window handle for the tab which is opened manually
• Fixed Allow append or start a new log file for chromedriver
• Fixed New Session doesn't invoke w3c mode if flag is in firstMatch

ChromeDriver 2.42

Supports Chrome v68-70

Changes include:

• Fixed ClickEelement in Mobile emulation
• Fixed whitelisted IPs with IPv4
• Fixed starting ChromeDriver with whitelisted-ips flag on Mac OS
• Fixed SetTimeout to accept both pre-W3C and W3C formats
• Fixed take element screenshot
• Fixed ChromeDriver is looking for Chrome binaries in a system PATH as well
• Fixed Maximize window and Full Screen
• Implemented log-replay feature. ( doesn't work for Android and Remote Browser yet )
• Fixed some error codes were not compliant to W3C standard
• Fixed console.log with multiple arguments not handled properly
• Fixed GetElementRect should allow doubles
• Fixed touch emulation

ChromeDriver 2.41

Supports Chrome v67-69

Changes include:

• Fixed issue when ChromeDriver runs with "whitelisted-ips" option
• Remote Debugging Port is returned in capabilities
• Implemented getting window size on Android
• Desktop Chrome launch error messages are improved
• ChromeDriver fails fast when unable to start Chrome binaries
• Close Window return value conforms with spec