feat: Allow type() and click() to select an element inside contenteditable.

[sainthkh]

• Closes Cannot focus element inside content editable element #2717
• Closes Click on table cell inside a contenteditable element does not behave as expected #7721
• It's the rework of feat: Place the caret at the start/end (all text elements) or clicked point (contenteditable only) #8529.

User facing changelog

When cy.type() and cy.click() were used against an element inside contenteditable, it only worked with the root contenteditable element. With this PR, this behavior is fixed. Users can freely work with elements inside contenteditable.

Additional details

• Why was this change necessary? => To change things inside contenteditable, it is sometimes necessary to work with elements inside it.
• What is affected by this change? => This is a breaking change. The behaviors of type() and click() changed slightly.
• Any implementation details to explain? => The change was a bit bigger than expected. I had to change the behavior of runAllCheck in actionability.js to ignore elements inside contenteditable.

How has the user experience changed?

<div id="a" contenteditable="true"><span id="b">abc</span>def</div>

cy.get('#a #b').type('123')
// => before: abcdef123
// => after: abc123def

PR Tasks

• Have tests been added/updated?
• Has the original issue or this PR been tagged with a release in ZenHub?
• Has a PR for user-facing changes been opened in cypress-documentation? => Add this to 6.0 changes doc.

[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]

flaky failure.

[kuceb]

awesome job

[Andarist]

@sainthkh would it be more accurate to say that "when a host contenteditable element is selected"? It feels a little bit like the comment doesn't match the condition because inner elements can still be contenteditable (.isContentEditable === true) but they won't pass this test here

[sainthkh]

I agree. It seems that When a selected element is contenteditable can better describe the code.