-
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
DatePicker popover close unexpectedly in Chrome when moving to min/max month #3603
Comments
Hi! Have you solved this problem? I encountered this problem too. |
I've got this too, here's a sandbox, without selecting any date, just move with the month arrows and it will close. Worth noting this work correctly on firefox, but on chrome it closes as soon the month reaches the min/max date |
Thanks for the sandbox @ejose19. Note that it only closes unexpectedly when no date is selected. If you first select a valid date, then reopen the picker and move to the min/max month, the popover stays open as expected. |
What's happening is the prev/next month button gets disabled when you reach the date bounds. In Chrome, this causes that It seems like the Firefox behavior might actually be a bug in FF (https://bugzilla.mozilla.org/show_bug.cgi?id=1650092). So the fix here needs to tweak In playing around with the keyboard accessibility of the component, I can see that it's not perfect, but I would still like to retain the functionality added in #2093 which closes the DateInput popover after a user TABs out of the last tabbable element in the popover. |
Steps to reproduce
In the dateInput component
The text was updated successfully, but these errors were encountered: