bug(cdk/testing): harnesses treat tabs different depending on test environment

Reproduction

https://travis-ci.org/github/e-hein/test-tabkey/branches

• without tab everything works as expected: last-working-sample-without-tab
  (build log|stackblitz)

• using tab will lead to different behavior: broken-by-using-the-tab-key
  (build log|changes|stackblitz)

• workaround: workaround-with-emulate-tab
  (build log|changes|stackblitz)

Expected Behavior

If I can switch from karma/jest to protractor I’d expect the same harness test to lead to the same results. In this case, I’d expected that senden TestKey.Tab to an TestElement it should select the next selectable element (or at least try to do so in the most common cases).

Alternative Behavior

Sending TestKey.Tab writes a \t into an input field in both environments.

Actual Behavior

• Sending TestKey.Tab in ProtractorEnvironment selects the next input (=expected Behavior)
• Sending TestKey.Tab in TestbedEnvironment does nothing (not even write \t)

Environment

• Angular: 9.1.9
• CDK/Material: cdk 9.2.4, material 9.2.4
• Browser(s): Chrome, Firefox
• Operating System (e.g. Windows, macOS, Ubuntu): Angular CLI: 9.1.9 Node: 12.18.0 OS: darwin x64 / Linux

[e-hein]

As stated at the end of #19946 further emulation of browser behavior is currently not in scope of angular/cdk. If you got a similar issue, I published my solutions at github.com/e-hein/emulate-tab and github.com/e-hein/emulate-key-in-browser (MIT License).

[angular-automatic-lock-bot[bot]]

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}