When a custom browser binary path location is provided with the binary_location field through the passed options param, while the "targeted browser version" log is retrieved and displayed according to this, the downloaded webdriver doesn't take into account this custom path and still relies on the default one.
Steps to reproduce
Have on the system the same browser twice, but with different versions.
Pass through binary_location the path of the non-default browser.
Effect: the version is pulled from the default one and is used to download a webdriver which might be incompatible with the selected custom different-in-version browser passed through the option.
⚠️ But first of all, you shouldn't have two identical browsers on the same machine of different versions. (and it's rare to find the need to pass a custom binary location as the browser is usually auto-detected by the webdriver itself)
When a custom browser binary path location is provided with the
binary_locationfield through the passed options param, while the "targeted browser version" log is retrieved and displayed according to this, the downloaded webdriver doesn't take into account this custom path and still relies on the default one.Steps to reproduce
binary_locationthe path of the non-default browser.⚠️ But first of all, you shouldn't have two identical browsers on the same machine of different versions. (and it's rare to find the need to pass a custom binary location as the browser is usually auto-detected by the webdriver itself)