fix: cy.contains and should('contain') handle backslash correctly.

[sainthkh]

• Closes cy.wrap(element).should('contain', textWithBackslash) fails #19116

User facing changelog

cy.contains and should('contain') handle backslash correctly.

Additional details

• Why was this change necessary? => Using backslash in cy.contains and should('contain') doesn't work.
• What is affected by this change? => N/A

Any implementation details to explain?

Using backslash breaks the Sizzle selectors below:

cypress/packages/driver/src/cy/chai.ts

Line 282 in b0fe8bf

const selector = `:contains('${escText}'), [type='submit'][value~='${escText}']`

cypress/packages/driver/src/dom/elements/find.ts

Line 277 in b0fe8bf

return `${filter}:cy-contains(${textToFind}), ${filter}[type='submit'][value~=${textToFind}]`

For example, strings like <asdf\ escape the quotation marks and breaks the query.

So, I escaped the quotation marks.

But I had to solve a few more problems like:

• redundant escapeQuotes functions. => create utils/escape.ts file and move them there.
• should('contain') message are not shown correctly. => I had to escape the double quotes first.

How has the user experience changed?

cy.get('#backslashes').contains('"<OE_D]dQ\\')
cy.get('#escape-backslashes').should('contain', '"<OE_D]dQ\\')

Before: Fails.
After: Passes.

PR Tasks

• Have tests been added/updated?
• [na] Has the original issue (or this PR, if no issue exists) been tagged with a release in ZenHub? (user-facing changes only)
• [na] Has a PR for user-facing changes been opened in cypress-documentation?
• [na] Have API changes been updated in the type definitions?
• [na] Have new configuration options been added to the cypress.schema.json?

[cypress-bot]

Thanks for taking the time to open a PR!

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.
• Become familiar with the Code Review Checklist for guidelines on coding standards and what needs to be done before a PR can be merged.

[sainthkh]

TODO is here because the test codes should be refactored a bit later.

The suite above format quotation marks actually has 3 subcategories:

• format quotation marks
• format strings
• escape markdown

The name doesn't explain well about the tests.

It'll be handled after this PR is merged.

[cypress-bot]

Released in 9.6.1.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v9.6.1, please open a new issue.