Confirm browser version support in Cypress 10+

[sync-by-unito[bot]]

Summary

Cypress does not open correctly in Chrome 84 and below due the use of some newer JS that is not polyfilled, for example String.prototype.replaceAll() . When those errors are removed there are some other CSS features that don’t seem to be supported fully also (testing in Chromium 77)

Running into this led to a discussion on Slack around whether supporting those older browsers is actually valuable to users and we should be testing in the oldest browsers we support?

https://cypressio.slack.com/archives/C02MW5QBD4K/p1653579277255099

Acceptance Criteria

This ticket is a placeholder to remind us to make a concrete decision. We should:

• update our list of supported browser versions, or
• test and maintain Cypress in the lowest versions of FF and Chrome that we support

We should not:

• state in our docs that Cypress supports chrome down to v64 if in reality we support 85 and up.

┆Issue is synchronized with this Jira Task by Unito ┆author: Mark Noonan ┆epic: Minor Bugs ┆friendlyId: UNIFY-1821 ┆priority: None ┆sprint: Backlog ┆taskType: Task

[rkriauciukas-freesat]

I am seeing also issues with Cypress not capturing network requests in Chromium 67.x nor Chromium 75.x, have to use the latest Chromium 90 to have network requests intercepted via cy.intercept.

So I would like to understand what are the actual fully supported Chromium versions and how far back in Cypress version do I have to go back to make it play nicely with Chromium 67.x, the specific version I need for testing like-for-like against Chromium on embedded system.

Thanks!

[github-actions[bot]]

This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided.

[github-actions[bot]]

This issue has been closed due to inactivity.