-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Conflicting information for minimum Chrome version 64 or 80 #5446
Comments
@jennifer-shehane same on this one. Can you confirm the update? |
This comment was marked as outdated.
This comment was marked as outdated.
I feel like there is a restriction that doesn't allow it to function after Chrome 80 that was introduced in v10. I can't remember exactly what it was nor can I find it. I'm fine with 80 though. Our previous strategy was to put the minimum version that Cypress will work - like we KNOW it breaks and doesn't function before that. If we want our strategy to be moreso - 'we will not support issues from these older browsers and work with you on it', then we could put a later Chrome version. Honestly the instances of issues I've seen on really old browsers feels pretty small, or nonexistent though....so I'm not sure this is an active problem. |
|
@MikeMcC399 Yes, this sounds fine to me |
|
Yes! There it is! |
Subject
Guides > Launching Browsers > Chrome Browsers
Description
In the section Guides > Launching Browsers > Chrome Browsers it states:
This contradicts the information in Guides > Launching Browsers > Browser versions supported in a previous section on the same page which says:
The documentation is therefore inconsistent and should be changed to state the same minimum Chrome version in all places - either
64
or80
.In terms of how Cypress is actually operating:
https://github.com/cypress-io/cypress/blob/0f9a150647146c3e63e14d298d7fcf7ad5c92b66/packages/launcher/lib/known-browsers.ts#L3-L10 shows:
so it appears that a minimum version of Chrome
64
is enforced in Cypress13.x
, not a minimum version of80
.The text was updated successfully, but these errors were encountered: