[Feature-Request] clickElemAt + hoverElemAt

[KearseTrevor]

Problem Definition

• Many components have specific behaviours depending on which portion of the element is being interacted with
• Specifically in some cases, a child component may rest in the very center of the parent component that is being interacted with
  • This child component will now be the main target of clickElem or hoverElem and can potentially hijack the expected experience of the target element for its own

Current workarounds

• dig through the shadowRoot of the parent to find a different child element that won't hijack the expected behaviour from parent (if one exists)
• home brew a clickAt or hoverAt solve by using elem.getBoundingClientRect() to generate a DOMRect() for position target information

Suggestion

• Provide new functions clickElemAt and hoverElemAt which will interact with the target element at some offset from their origin instead
• Example branch

[d2l-github-release-tokens]

🎉 This issue has been resolved in version 1.26.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀