Skip to content
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

Is there a Cypress version that supports Chrome 66 browser? #5887

Closed
Whiskeyi opened this issue Aug 1, 2024 · 7 comments
Closed

Is there a Cypress version that supports Chrome 66 browser? #5887

Whiskeyi opened this issue Aug 1, 2024 · 7 comments

Comments

@Whiskeyi
Copy link

Whiskeyi commented Aug 1, 2024

Description

I want to do automated testing on Chrome 66 based pages, but I encountered an error during actual execution.The version of Cypress I am using is 10.11.0.Can I change a version of Cypress to solve this problem?

URL of Issue(s)

https://docs.cypress.io/guides/guides/launching-browsers#Chrome-Browsers

Steps to replicate

No response

Env

Linux_x64_Chrome 66

Additional Information

No response

The document states that it is supported.
image

@Whiskeyi
Copy link
Author

Whiskeyi commented Aug 1, 2024

Error call stack:
image

@MikeMcC399
Copy link
Contributor

MikeMcC399 commented Aug 1, 2024

@Whiskeyi

  • Chrome 66 was released on April 17, 2018. This is quite a long time ago.

  • In the Changelog for Cypress 10.8.0 there is an entry which mentions this version of Chrome. So you might like to try Cypress 10.8.0:

    • Fixed a regression introduced in Cypress 10.0.0 where Cypress was incompatible with Chrome v64 - v70. Fixes #23509.
  • There is an open issue concerning conflicting information in the documentation about whether Chrome 64 or 80 is the minimum version. See Conflicting information for minimum Chrome version 64 or 80 #5446. Despite what it says, you should probably consider Chrome 80 as the lowest version which works with current Cypress versions 13.x.

  • The nearest Cypress Docker image would be cypress/browsers:chrome67 however that would be problematic to use, since it is based on Debian 8 (end-of-life June 2020) and Node.js v8.10.0 (end-of-life December 2019). Cypress currently requires minimum Debian 11 and Node.js 18.x.

@Whiskeyi
Copy link
Author

Whiskeyi commented Aug 2, 2024

@MikeMcC399 Thanks a lot for your reply!
After I replaced it with version 10.8.0, the error still persists, and the error is not as described in issue cypress-io/cypress#23509

image

Chrome 66 was indeed released a long time ago, but our automated testing has this scenario to test lower version browsers

Based on your description, I will try Chrome 67 again later.

I hope that the minimum compatible version of the browser can be clearly stated in the documentation in the future.

@MikeMcC399
Copy link
Contributor

MikeMcC399 commented Aug 2, 2024

@Whiskeyi

It will be difficult to get support for your testing because Node.js 14.x is no longer supported. It entered end-of-life in April 2023.

I hope that the minimum compatible version of the browser can be clearly stated in the documentation in the future.

@MikeMcC399
Copy link
Contributor

@Whiskeyi

There was some confusion about older Browser support which is now clarified in the documentation.

The statement is that you can test against Chrome 64 and later with the latest version of Cypress 13.x. To use cypress open you need a minimum of Chrome 80.

Since issues in this repository are only about documentation, this issue should be closed now.

In any case the problem with Fetch.enable may be a problem with Chrome, not a problem with Cypress. If you feel this is a bug in Cypress you should open a new issue in https://github.com/cypress-io/cypress/issues

@Whiskeyi
Copy link
Author

Whiskeyi commented Aug 6, 2024

ok, thank you!

@Whiskeyi Whiskeyi closed this as completed Aug 6, 2024
@Whiskeyi
Copy link
Author

@MikeMcC399 The issue with the error is due to our use of experimental features(experimentalSessionAndOrigin configuration option ), which are not supported in lower versions of browsers. After disabling this option, the issue has been resolved.
In the 12.0.0 changelog document, I see that this configuration item has been removed and automatically enabled。
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants