-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[🚀 Feature]: We should stick to main chrome channel instead of CFT (Chrome for Testing) #2041
Comments
@amardeep2006, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
We already moved back to the regular Chrome installation, and we will keep using it. One of the main use cases of CfT is to allow users to test with previous versions to verify regressions. Which they can also do by selecting the correct tag in our images. |
CfT was introduced via #2018 and very fast it was rolled back in #2033 due to the issue reported. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Feature and motivation
I am sharing my thoughts that why we should stick to existing method of Chrome installation untill there is apt-get way to install CFT.
We are already getting chrome driver from CFT endpoints which is tried tested and stable method.
We should stick with existing method for stability in my opinion untill Google provides an easy way ( e.g. ppa repo) for CFT and we are able to install via apt-get OR we have some solid reason to do so.
Please share your thoughts .
Usage example
Stability of chrome.
The text was updated successfully, but these errors were encountered: