You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 23, 2024. It is now read-only.
Describe the bug
When I call userEvent.type in a play function, hot reloading the story causes the typing to update the form value but not trigger onChange.
doing things that take up time --- even an entire second --- doesn't prevent this behavior, but using userEvent.hover before userEvent.type might make it less likely. It's an intermittent bug.
To Reproduce
Steps to reproduce the behavior:
Build a story with Chakra UI inputs that has a search input with an onChange
add a userEvent.type and some expect that shows that the onChange was triggered
Cause storybook to hot-load (it may fail)
re-run the action (it succeeds)
Expected behavior
userEvent.type should always trigger onChange
Screenshots
After automatically running the play function because it was edited:
After hitting "rerun" on the test:
Describe the bug
When I call
userEvent.type
in a play function, hot reloading the story causes the typing to update the form value but not triggeronChange
.doing things that take up time --- even an entire second --- doesn't prevent this behavior, but using
userEvent.hover
beforeuserEvent.type
might make it less likely. It's an intermittent bug.To Reproduce
Steps to reproduce the behavior:
expect
that shows that the onChange was triggeredExpected behavior
userEvent.type should always trigger onChange
Screenshots
After automatically running the play function because it was edited:
After hitting "rerun" on the test:
System
Additional context
await
the userEventThe text was updated successfully, but these errors were encountered: