Add granular event hooks (for use in closing Dialog
s)
#911
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.
Depends on #910
Fixes #900
Part of #77
This PR decomposes the functionality of
useElementShouldClose
into three separate, more-generic hooks, and aligns withuseArrowKeyNavigation
in the use ofListenerCollection
for managing event listeners. This will allow more nuanced control forDialog
s.There's some opportunity to DRY this out some in the future (especially in tests), but I started with the simplest approach possible here.
Just like with
Dialog
, I imagine we might make these hooks part of the package's public API (and deprecateuseElementShouldClose
). But let's do that later and separately.