You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems to me that the UX would greatly improved if there were some reaction when clicking in the styled 'input' area, marked by the class "react-date-picker__button__input". This is very evident when inputs are taking the whole width:
My expectation is that clicking in that area would focus the first text input.
The text was updated successfully, but these errors were encountered:
Yeah that seems like a neat idea. It's what native input does by default when expanded beyond what's necessary, and React-Date-Picker's aim is to behave as closely to a native input as possible. This will be out with the next release of React-Date-Picker, React-DateTime-Picker, React-Time-Picker and their range versions, too.
Hi, I'm adding this note for future reference, since I found a workaround for this issue.
You can create a state for isOpen and change it by clicking on the DatePicker component. The isOpenprop only affects the component when the value change, so it doesn't override other behaviours, like clicking out. BUT for the same reason, you should update the state when the calendar is closed, or it will only work once.
It seems to me that the UX would greatly improved if there were some reaction when clicking in the styled 'input' area, marked by the class "react-date-picker__button__input". This is very evident when inputs are taking the whole width:
My expectation is that clicking in that area would focus the first text input.
The text was updated successfully, but these errors were encountered: