-
Notifications
You must be signed in to change notification settings - Fork 2.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
DateRangePicker shortcuts incorrectly dismiss popovers #3338
Comments
I don't fully understand, can you post a video / gif of the problem and some example code? In the example you linked, the popover does not get dismissed unless you enable the "close on selection" switch. |
I looked at this more closely through #3668 and I see the OP issue where the popover is dismissed by the |
Hi people! I've thrown together a sandbox to demonstrate how the date range picker closes any enclosing popover when a shortcut date is selected. Hope this helps towards finding a fix :) |
As a quick workaround:
have to also remove a class on each range change because it is getting added back on shortcut select |
Environment
Steps to reproduce
Example
https://blueprintjs.com/docs/#datetime/daterangeinput
Actual behaviour
Popover is dismissed
Expected behaviour
Popover should not be dismissed
Possible solution
Use
shouldDismissPopover
instead ofClasses.POPOVER_DISMISS_OVERRIDE
.The text was updated successfully, but these errors were encountered: