feat: Date Picker #416
Replies: 5 comments 6 replies
-
|
Definitely this is required |
Beta Was this translation helpful? Give feedback.
-
|
This will be available in the next version. Stay tuned... |
Beta Was this translation helpful? Give feedback.
-
|
Looks great.
One observation for your consideration:
If I have to enter date of birth, I have to either click the arrow to reach
upto my year and month of birth or else select my day and month of birth in
the current year and once the date is selected in the text box, manually
change the year.
Can you please put options as available in the Fluent UI react control.
Please refer to the screenshot below:
[image: image.png]
Thanx & Regards
Parash
…On Tue, Jun 13, 2023 at 2:44 AM Denis Voituron ***@***.***> wrote:
Interesting. Thanks for your feedback. I'll add a min-width value to avoid
this issue on mobile.
—
Reply to this email directly, view it on GitHub
<#416 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHKTT4ZVLG7YKUHDCGBBCGLXK6BDJANCNFSM6AAAAAAYVMK2CY>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Looks nice, but does it look possible for the DatePicker to be bound to the |
Beta Was this translation helpful? Give feedback.
-
|
Fluent UI DatePicker accepts legacy DDMMYYYY input .how to strictly reject it ? We have a legacy backend product that is over 30 years old, and it historically accepts dates entered in the numeric DDMMYYYY format (for example, 01012025). We are currently modernizing the system and introducing the Fluent UI DatePicker on the frontend. Problem When users type 01012025 directly into the Fluent UI DatePicker input, the component does not reject or modify this input. Unlike other date formats which are reformatted or validated by the DatePicker this legacy numeric format is effectively ignored and remains unchanged. Our goal is to explicitly reject this format and allow only properly formatted dates, such as locale-based formats (MM/DD/YYYY or DD/MM/YYYY). Many of our users are habituated to typing dates in this legacy way, but as part of the modernization effort, we want to prevent the use of numeric DDMMYYYY input going forward and enforce stricter date validation. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
🙋 Feature Request
Would love to see functionality to bind the calendar to an input element. Would be nice to have this configurable between these input types:
🤔 Expected Behavior
Input component with Calendar popover for selecting dates/times.
Beta Was this translation helpful? Give feedback.
All reactions