-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
type('{enter}') does not fire click event #19541
Labels
Comments
1 task
mjhenkes
added
type: bug
stage: ready for work
The issue is reproducible and in scope
labels
Jan 5, 2022
@jamime, Thanks for the reproducible repo. I've confirmed this is an issue in 9.2.0 |
1 task
cypress-bot
bot
added
stage: needs review
The PR code is done & tested, needs review
and removed
stage: ready for work
The issue is reproducible and in scope
labels
Jan 17, 2022
cypress-bot
bot
added
stage: waiting
stage: needs review
The PR code is done & tested, needs review
and removed
stage: needs review
The PR code is done & tested, needs review
stage: waiting
labels
Jan 25, 2022
cypress-bot
bot
added
stage: pending release
and removed
stage: needs review
The PR code is done & tested, needs review
labels
Jan 31, 2022
The code for this is done in cypress-io/cypress#19726, but has yet to be released. |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Current behavior
When the target element is a button
type('{enter}')
fires the eventsNote the first "click" is from activating the button.
Desired behavior
When the target element is a button
type('{enter}')
should fire the eventsNote the first "click" is from activating the button.
Test code to reproduce
https://github.com/jamime/cypress-test-tiny
Cypress Version
9.2.0
Other
https://w3c.github.io/uievents/#event-type-keydown
Once the cypress test has failed, if you click "reset", then click the second button and press "Enter" you will see the correct output.
The text was updated successfully, but these errors were encountered: