Fixes #2383

[Ankush263]

Fixes #2383

Changes:

I have verified that this pull request:

• [✅] has no linting errors (npm run lint)
• [✅] has no test errors (npm run test)
• [✅] is from a uniquely-named feature branch and is up to date with the develop branch.
• [✅] is descriptively named and links to an issue number, i.e. Fixes #123

[welcome]

🎉 Thanks for opening this pull request! Please check out our contributing guidelines if you haven't already.

[Ankush263]

Should I need to change something here??

[lindapaiste]

We’ve gotten a lot of PRs in the past few days and I haven’t had a chance to review them all yet!

We were previously looking at the keyup event. With your fix we are now looking at both the keydown (fired first) and the keyup. Is it necessary to check for “enter” on both events? It seems a little odd, but I need to check out your branch and play with it to see how it behaves.

[Ankush263]

Yeah, it's odd to use both keyUp and keyDown, I tried different approaches, but this works perfectly .

[raclim]

Since it's been a while since this PR has been updated, I've marked it with a "closing soon" label, which signifies that this PR will be closed in 10 days. Please feel free to revisit this to make any further updates or indicate that you would like to keep this open!