-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[BUG] - Unable to dismiss DatePicker after date selected by Preset #3457
Comments
@wingkwong i would like to take up the issue. |
@kajaveaniruddha Thanks. Please feel free to ping us in discord if you have any question. |
@wingkwong I have been on the project for for past few days, I have identified the parts of files I have to work on (date-picker.stories.tsx, date-picker.tsx, use-date-picker.ts). I am unable to target the CalendarTopContent elements (those are the buttons like today, next week etc). Can you help with something so that i can proceed ahead ? |
Hi @wingkwong , what is the expected behavior in this? Is it to automatically close the |
@ShrinidhiUpadhyaya from my understanding, users want to dismiss the date picker after clicking preset buttons, just like when you select a date. however, i think it's better to cover both case. |
@ShrinidhiUpadhyaya this issue has been assigned to someone else. Next time please communicate with the assignee before your implementation. |
@wingkwong can you share the discord community link ? |
NextUI Version
2.4.2
Describe the bug
How to dismiss DatePicker after update the value from Preset?
Click selector button after update the value, but does not work.
popoverProps -> onOpenChange
also does not trigger when DatePicker is show.Your Example Website or App
https://codesandbox.io/p/devbox/vigilant-tharp-wm48j3?file=%2FApp.tsx%3A71%2C15
Steps to Reproduce the Bug or Issue
Expected behavior
I expected to dismiss DatePicker by programmatically.
Screenshots or Videos
No response
Operating System Version
Windows
Browser
Chrome
The text was updated successfully, but these errors were encountered: