Need to be able to get minimum supported Chrome version from command line
Reported by
is...@saucelabs.com,
Mar 23 2018
|
|||||||||
Issue descriptionSteps to reproduce the problem: 1. Try running CD against an old version of Chrome What is the expected behavior? From CLI, I would like to be able to do something like `chromedriver --minimum-chrome-version` and get reasonable output saying something like `63.2.4.6`. What went wrong? As it stands, for a particular version of CD you need to check out the release commit, then go into `src/chrome/test/chromedriver/chrome/version.cc` to find the version. We end up having to keep a running list of CD version -> Chrome version mappings (see https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/web/chromedriver.md). Did this work before? No Chrome version: 65.0.3325.181 Channel: stable OS Version: OS X 10.13.3 Flash Version: I am happy to do this work, I just want to solicit others' opinions before embarking on it.
,
Mar 26 2018
isaac@ -- Could you please confirm on which platform the issue is observed. Is it on Chrome for Android or Chrome for Mac. If it is on Android, could you please share the device details including the OS version. Thanks!
,
Mar 26 2018
We (The Appium Project) use it for Android. The feature request is for any version of Android and any version of Chrome. The desire is to be able to query a particular Chromedriver executable and get back the minimum version of Chrome that is supported. This information is in the Chromedriver, it is just difficult to get out and at the moment require external mapping. The issue we are working around is that supporting older Android devices with older Chrome versions on them require switching which Chromedriver is used, and we would like to not have to get the Chromedriver version, then look into our map for what the minimum Chrome version it supports is. This information should be retrievable from the Chromedriver itself.
,
Mar 26 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 27 2018
isaac@ -- Thanks for the reply. Updating the issue accordingly so that the issue gets addressed. Thanks!
,
Mar 30 2018
,
Dec 19
,
Dec 19
Tatiana: Could you please take care of this issue? Thanks!
,
Dec 27
,
Dec 27
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/2c6a0bee4f514c6e00f998724dbca4d8fc4b6e9c commit 2c6a0bee4f514c6e00f998724dbca4d8fc4b6e9c Author: Tatiana Buldina <buldina@chromium.org> Date: Thu Dec 27 19:45:04 2018 [ChromeDriver] Add minimum supported Chrome version argument to command line Bug: 825165 Change-Id: I5fd47663dd94d808e8be8123258656a790632cbd Reviewed-on: https://chromium-review.googlesource.com/c/1391357 Reviewed-by: John Chen <johnchen@chromium.org> Commit-Queue: Tatiana Buldina <buldina@chromium.org> Cr-Commit-Position: refs/heads/master@{#619056} [modify] https://crrev.com/2c6a0bee4f514c6e00f998724dbca4d8fc4b6e9c/chrome/test/chromedriver/server/chromedriver_server.cc
,
Dec 27
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by pnangunoori@chromium.org
, Mar 26 2018