Download Chrome Driver

download chrome driver

Previous iterations of Chrome

These are the ChromeDriver versions that work with older Chrome versions

download chrome driverChromeDriver 114.0.5735.90

Compatible with Chrome 114

Refer to the release notes for further information.

Chrome version 114 is supported by

ChromeDriver 114.0.5735.16.

Refer to the release notes for further information.

Chrome version 113 is supported by ChromeDriver 113.0.5672.63.

Issue 4205 has been resolved: Classic and BiDi [Pri-1] have the same object ids.
Issue 4302 has been fixed: Don’t presume that Mapper is in ExecuteGetWindowHandles [Pri-1]’s initial tab. download chrome driver
Issue 4356 has been fixed: Chrome 110 is not using the “download.default_directory” pref setting [Pri-1].
Refer to the release notes for further information.

Chrome version 113 is supported by ChromeDriver 113.0.5672.24.

Issue 4205 has been resolved: Classic and BiDi [Pri-1] have the same object ids.
Issue 4302 has been fixed: Don’t presume that Mapper is in ExecuteGetWindowHandles [Pri-1]’s initial tab.
Issue 4356 has been fixed: Chrome 110 is not using the “download.default_directory” pref setting [Pri-1].
Refer to the release notes for further information.

Chrome version 112 is supported by ChromeDriver 112.0.5615.49.

Issue 3517 has been resolved: Turn on the print function for non-headless [Pri-]
Issue 4419: Significant speedometer overhead when using Chromedriver [Pri-3] has been fixed.
Refer to the release notes for further information.

download chrome driver

Chrome version 112 is supported by ChromeDriver 112.0.5615.28.

The Chromedriver version 110.0.5481.77 session issue with the –headless and –user-data-dir options has been fixed (issue 4357). [Pri-1]
Refer to the release notes for further information. 

Chrome version 111 is supported by ChromeDriver 111.0.5563.64.

Issue 4216 has been fixed: Use ChromeDriver with the customized BiDiMapper [Pri-]
Issue 4300 has been resolved: the window handle works with both Classic and BiDi. [Pri-]
Issue 4325 has been resolved: The way toJSON is handled in call_function.js’s jsonSerialize deviates from the norm. [Pri-] download chrome driver
Issue 4330: DCHECK fails at DevToolsClientImpl has been fixed. [Pri-] AddListener
Refer to the release notes for further information.

Chrome version 111 is supported by ChromeDriver 111.0.5563.41.

Refer to the release notes for further information.

Chrome version 111 is supported by ChromeDriver 111.0.5563.19.

Issue 4216 has been fixed: Use ChromeDriver with the customized BiDiMapper [Pri-]
Issue 4300 has been resolved: the window handle works with both Classic and BiDi. [Pri-]
Issue 4325 has been resolved: The way toJSON is handled in call_function.js’s jsonSerialize deviates from the norm. [Pri-]
Issue 4330: DCHECK fails at DevToolsClientImpl has been fixed. [Pri-] AddListener download chrome driver
Refer to the release notes for further information.

Chrome version 110 is supported by ChromeDriver 110.0.5481.77.

Issue 4193: Android 13 [Pri-] failed to launch a fresh session has been fixed.
Issue 4272 has been fixed: WebSocket should interpret code=0 as a FIN indication. [Pri-]
Issue 4276 has been resolved: ChromeDriver connectivity difficulties have been fixed [Pri-]
Problem 4295: ChromeDriver with “webSocketUrl”: true is racy has been fixed. [Pri-]
Issue 4297: ChromeDriver Bidi serializes wrongly [Pri-] has been resolved.
Refer to the release notes for further information.

Chrome version 110 is supported by ChromeDriver 110.0.5481.30.

Issue 4193: Android 13 [Pri-] failed to launch a fresh session has been fixed.
Issue 4272 has been fixed: WebSocket should interpret code=0 as a FIN indication. [Pri-]
Issue 4276 has been resolved: ChromeDriver connectivity difficulties have been fixed [Pri-]
Refer to the release notes for further information.

Version 109.0.5414.74 of ChromeDriver
Compatible with Chrome 109

Issue 4179 has been resolved: a BiDi session needs to accommodate several connections. [Pri-]
Issue 4203 has been resolved: Enhance credit data [Pri-] download chrome driver
Refer to the release notes for further information.

Chrome version 109 is supported by ChromeDriver 109.0.5414.25.

Issue 4179 has been resolved: a BiDi session needs to accommodate several connections. [Pri-]
Issue 4203 has been resolved: Enhance credit data [Pri-]
Refer to the release notes for further information.

Chrome version 108 is supported by ChromeDriver 108.0.5359.22.

Fix the failing WPT test_top_level_and_one_child [Pri-] to resolve bug 4204.
Issue 4215 has been fixed: change the build name of chromedriver_mac64_m1 to chromedriver_mac_arm64. [Pri-]
Issue 4221 has been fixed: When a click command ends the browser, it crashes [Pri-] download chrome driver
Refer to the release notes for further information.

Chrome version 107 is supported by ChromeDriver 107.0.5304.18.

Issue 4180 was fixed: Don’t handle any BiDi commands until you’re informed that BiDiMapper has begun [Pri-]
Fix for problem 4198: ChromeDriver BiDi shouldn’t presume that the first tab is always BiDiMapper [Pri-]
Issue 4207: WebDriver error during WPT [Pri-1] has been fixed.
Refer to the release notes for further information.

Chrome version 75 is supported by ChromeDriver 75.0.3770.8.

The most obvious modification is that ChromeDriver now launches by default in a mode that complies with W3C standards. Other modifications consist of: download chrome driver

A issue that raised the blur event twice during element clear has been fixed.
As required by the W3C standard, the capability loggingPrefs was renamed to goog:loggingPrefs.
Error handling in W3C mode was fixed.
Creating cookies correctly without a leading dot in the domain name
enables script timeout with null.

Fixed Element Send Keys command for’multiple’ attribute file input
When there is no active element, the “no such element” error is returned by the Get Active Element command.
Navigation to a faulty URL was fixed, resulting in a “invalid argument” error.
When an invalid session ID is received, the HTTP status code is fixed.
When an input parameter is absent or distorted, the error answer is fixed.
To handle line-oriented JavaScript comments, the Execute Script command was fixed. download chrome driver
Refer to the release notes for further information.

Chrome version 74 is supported by ChromeDriver 74.0.3729.6.

A Windows problem that produced an unexpected debug.log file has been fixed.
Mouse clicking and drag/drop functionality inside SVG documents has been fixed.
Cache-control header was added to ChromeDriver replies.
The sort of error that occurs when a click is intercepted by another element has been fixed.
A issue that made ChromeDriver malfunction on Linux machines lacking /dev/shm has been fixed.
Several double-click event kinds have been fixed.
The Get Sessions command was fixed.
Error checking in the Switch To Frame instruction was fixed.
The Get Page Source command has been fixed.
Refer to the release notes for further information.

Chrome version 73 is supported by ChromeDriver 73.0.3683.68.

A issue that caused unexpected debugging has been fixed. Windows log file
In certain cases, the Execute Script command gave a fixed error code.
Cache-control header was added to ChromeDriver replies.
set the HTTP server to maintain the connection by default.
The Close Window command has been fixed to properly respond to user prompts.

Improved adherence to specifications for handling timeout values; fixed error code issued when passing keys to disabled elements
Enhanced Add Cookie command spec compliance
Longer listening queue for HTTP servers fixed Does the v0 shadow DOM contain the Element Displayed command?
An additional caution regarding Element The log file shows a clear command behavior change.
The Execute Script command has been fixed to convert documents correctly. everything into JSON format Better management of incorrect element references
Refer to the release notes for further information.

Chrome v71-73 is supported by ChromeDriver 2.46.

In certain cases, the Execute Script command gave a fixed error code.
set the HTTP server to maintain the connection by default.
The Close Window command has been fixed to properly respond to user prompts.
When passing keys to a disabled element, a fixed error code was given.
Better handling of timeout values in accordance with specifications
Enhanced Add Cookie command spec compliance

Enhanced Switch to Frame command spec compliance Longer HTTP server listening queue
The v0 shadow DOM’s Is Element Displayed command has been fixed.
Double-clicking an element was fixed.
A notice of a change in the behavior of the Element Clear command was added to the log file.
The Execute Script command has been fixed to convert documents correctly. everything into JSON format Better management of incorrect element references
Refer to the release notes for further information.

Chrome v70–72 is supported by ChromeDriver 2.45.

Fixed New Session does not adhere to the specifications.
Repaired If Chrome and ChromeDriver versions are incompatible, ChromeDriver shouldn’t start Chrome.
Repaired When an invalid location is provided, the Find Element command produces the incorrect error code.
Repaired There are some incorrect ChromeDriver status codes.
Repaired JS compilation fault within WebViewImpl: MouseEvents DispatchTouchEvents
User prompts should be handled by fixed window size commands.
Repaired ChromeDriver fails to properly launch Chrome when using the “user-data-dir=” Chrome option.
Repaired Status commands do not adhere to specifications.
Repaired Include strictFileInteractability support.

Chrome v69–71 is supported by ChromeDriver 2.44.

Mac’s WindowMaximize was fixed.
‘alert open error’ for window handle call was fixed.
In W3C mode, Fixed Element Send Keys ought to receive the “text” property.
Is Element Enabled’s fixed XML special case is not handled according to specification.
Get Element CSS Value’s fixed XML special case is not handled according to specification.
Checking for incorrect input is necessary for the Fixed Set Window Rect.
New unhandled PromptBehavior modes are now supported.

Chrome v69–71 is supported by ChromeDriver 2.43.

Among the modifications are:

Repaired Proxy configuration parsing does not adhere to standards.
Repaired The instruction to launch the app is erratic.
Repaired The iFrame element’s screenshot was taken wrongly.
ChromeDriver has been updated to allow window resizing via a remote connection.
Repaired Clear element Fixed does not handle error codes. Not waiting for the element to become visible
Repaired There is no implementation of the Get element property.
Repaired It is not spec compliant to switch to Frame.

Spec-compliant error codes are not returned by the Fixed Execute Async Script.
Spec-compliant error codes are not returned by the Fixed Execute Script.
ExecuteGet’s fixed error code does not adhere to the specification.
Repaired Spec-compliant error codes are not being returned by Send Alert Text.
When an input type=”date” has clear() fixed, it assumes the element is not changeable by the user. download chrome driver
Repaired Chromedriver retrieves the tab’s window handle when it is manually opened.
Repaired Permit adding or starting a new ChromeDriver log file.
Repaired When the flag is in firstMatch, the next session does not enter W3C mode.

Chrome v68–70 is supported by ChromeDriver 2.42.

Among the modifications are:

ClickEelement was fixed on the mobile emulator.
IPv4-fixed whitelisted IPs
ChromeDriver’s whitelisted-ips flag was fixed when it started on Mac OS.
SetTimeout was fixed to support both pre-W3C and W3C formats.
A screenshot of the fixed take element
Additionally, Fixed ChromeDriver searches a system PATH for Chrome binaries. download chrome driver
Fixed Full Screen and Window Maximization
incorporated the log-replay function. (Remote browser and Android do not currently support it.)
Several error codes that did not adhere to W3C standards were fixed in the console. Multiple argument logs are not handled correctly.
Repaired GetElementRect ought to permit doubles.
Emulation of fixed touch

Chrome v67-69 is supported by ChromeDriver 2.41.

Among the modifications are:

Issue resolved while using the “whitelisted-ips” option in ChromeDriver
The ability to use the Remote Debugging Port has been restored.
Android desktop Chrome start error messages have been improved with the implementation of window size retrieval.
When Chrome binaries cannot be started, ChromeDriver quickly fails.
The Close Window return value complies with the specifications.

Leave a Reply

Your email address will not be published. Required fields are marked *

Back To Top