[datetime] fix: clicking shortcuts no longer dismisses popovers #5219
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.
Fixes #3338
By default MenuItem has
Classes.POPOVER_DISMISS
added to the component, controlled by theshouldDismissPopover
prop.The
Shortcuts
component clearly intended to block this behavior through the use ofClasses.POPOVER_DISMISS_OVERRIDE
.However, per the
Popover
andPopover2
components, a dismiss inside an override still dismisses.Luckily,
MenuItem
has a prop just for this!Changes proposed in this pull request:
Stop datepicker shortcuts from dismissing popovers
Reviewers should focus on:
If this correctly dismisses popovers and aligns with the author's original intent.
Screenshot
(Imagine a picture of a happy dev, not having to insert some hack to strip the dismiss class from the child menuitem)