[Spike]: Tab key support

[jennifer-shehane]

What would you like?

We'd like to spike into some open questions around tab key support in order to drive future decisions on its implementation. The outcome of this spike should be findings brought back to the team to discuss next steps for requirements.

Open Questions

• Verify and document behavior of type() command when focus of the subject changes mid-type.
  • What is yielded as the subject of the original command if focus changes?
• Verify and document 'typeable' checks of .type() and which would not be appropriate to enforce for tab key actions.
• Verify behavior of cy.document().type() and cy.window().type()
• Investigate Webdriver BiDi support for 'tab' key actions
  • Which event is best?
    • PerformActions: https://w3c.github.io/webdriver-bidi/#command-input-performActions
    • https://webdriver.io/docs/api/webdriver/#performactions
  • What is the current browser support for the API in BiDi?
    • Is the behavior different per browser?
  • Can we dispatch the event to the correct AUT window?
  • Is 'odd' DOM handled as expected? (iframes, shadow DOM, etc)
  • Any extra considerations for this command within cy.origin?
• Investigate implications of sticky activation when native events are used vs simulated events. (See this existing issue that only pops up when native events are used over simulated ones)

Secondary Questions

• Effort, benefit, and impact of switching other 'type' events to native events. (Not necessary to ship tab key support)

Why is this needed?

To prepare work for #299

Other

No response