InputControl: Make onChange
observable in Storybook
#60055
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Required for testing IME keydown handling (follow-up to #59081)
What?
Enhances the Storybook stories for InputControl so
onChange
events can be tested using the Actions panel.Why?
We generally want all our
onChange
events to be testable in Storybook.Testing Instructions
In trunk Storybook, we can see that change events aren't logged in the Actions panel.
isPressEnterToChange
prop and reload.onChange
should only be logged after blurring the input or hitting the Enter key. TheonValidate
calls should also be logged.