Orphaned Test Replay limitations link

[MikeMcC399]

Description

Issue

The target https://docs.cypress.io/faq/questions/cloud-faq#Is-everything-captured-and-replayed-in-Test-Replay was removed by PR #5985. It was last present in 3f2c22c.

It is used in:

• https://docs.cypress.io/accessibility/core-concepts/how-it-works#Powered-by-Test-Replay

  Because Cypress Accessibility uses data captured through Cypress Test Replay, it is subject Test Replay limitations.

• https://docs.cypress.io/ui-coverage/get-started/introduction#How-it-Works

  Because Cypress Accessibility uses data captured through Cypress Test Replay, it is subject to any limitations of Test Replay data captured and browser support.

Clicking on the link leaves the reader stranded with no content discernible which matches the theme: "limitations of Test Replay".

It used to contain the following content:

---

Is everything captured and replayed in Test Replay?

Our aim is to create an impactful debugging experience that covers the most ground for users. We will continue to expand support. Currently Test Replay does not support the following:

DOM elements

• Video (see issue)
• Audio (see issue)
• Objects that do not have type="image/svg+xml" (see issue)
• Shadow DOM with slotAssignment="manual" (see issue)
• Shadow DOM canvas (see issue)

Browsers

• WebKit browser (Safari) (see issue)
• Firefox browser (see issue)

Other

• Server sent events (see issue)
• Web sockets (see issue)
• localStorage & sessionStorage (see issue)
• Cookies (see issue)
• Console props of Cypress commands outside of cy.request() (see issue)

[MikeMcC399]

@jennifer-shehane

The alternatives would be:

1. Remove the paragraphs which reference "Test Replay limitations"
2. Add something back which describes limitations

This is more of an editorial decision / action than a simple editing task, so I leave its resolution to the Cypress.io team.

PS Happy holidays!

[jennifer-shehane]

@MikeMcC399 These links should link to this content: https://docs.cypress.io/cloud/features/test-replay#How-Test-Replay-Works I'd update the link wording to be 'it is subject to the [data captured in Test Replay]'