Web DatePicker: Time selection #9545
Comments
aftab-hassan
added
Needs: Backlog review
Type: Feature
and removed
Needs: Triage 🔍
labels
|
@gavinbarron thank you for submitting a feature request. cc: @micahgodbolt @lorejoh12 (coming from the Teams thread where we discussed a Calendar input with time input included : FYI |
What about |
|
We would also welcome an official UI Fabric time picker component to use in our product. Preferably independent of the Calendar or DatePicker components. |
|
In my opinion there are use cases for both a time picker and datetime
picker in addition to the DatePicker.
The MWF Datetime picker control can be configured in Date Picker, DateTime
Picker, and Time Picker modes.
Given the current state of the UI Fabric Web controls library I'd suggest
that an independent TimePicker control be shipped initially as this would
not imply or need any interface change to DatePicker. If a consumer needs a
Date Time Picker it should be trivial to compose one with these two
controls. A future update could deliver a composite control as part of the
library.
Heck, I'd even be happy to put my hand up and write the composed control.
…On Thu, Jul 11, 2019, 1:17 AM Hlynur Tryggvason ***@***.***> wrote:
We would also welcome an official UI Fabric time picker component to use
in our product. Preferably independent of the Calendar or DatePicker
components.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#9545>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABWK6HCSAVCB4YXWEOUUAP3P63UBNANCNFSM4H2S4YDA>
.
|
|
Most teams I talk to say that if they need date and time picking that they will create an HOC that combines a date picker and some sort of time picking (dropdowns usually). This is how outlook is currently doing it, so I don't think design is content with that solution and isn't investing in something different. If it ain't broke, don't fix it. |
Makes sense not to change the existing component--but why not merge the HOC back into Fabric? It's a generic enough requirement that HTML even supports datetime inputs natively. |
|
The HTML version is quite similar to ours in the picking experience.
The main difference is that they place the time picking inside of the input rather than separate controls.
As far as canonizing something in Fabric, it's possible we'll get there eventually. But its not a huge priority due to the ability to easily create a usable control yourself.....which also gives you flexibility to suit it to your application needs. |
|
Also interested in a DateTime picker control. Thanks! |
|
Would love to see a DateTime control as well. Or even a separate TimePicker. |
|
Yammer is also interested in either a combined DateTimePicker, or a separate TimePicker component. |
|
It would be great to have a TimePicker component |
|
I am using web version of Fluent UI react version 7 in my web application. I am not able to find time picker control yet. Are you planning to release this timepicker component? |
|
What's the update on timePicker? Is there a plan for it to be developed in near future? I and my team have chosen fabric and so far find it great, just a catch that we get to have a timePicker which is a requirement from our client. Will really appreciate if its added soon. |
|
Hey guys, any updates on this? This is really needed feature |
|
Is this a work in progress component? Any updates? |
|
Interested in an update as well |
|
We are using fluent-ui in our project. We needed Timepicker control with Datepicker. Is there any updates on this? We are really looking forward it. If no updates then what can be used instead of it? |
|
I don't think this is something we currently have on our roadmap, but @JustSlone or @paulgildea (or @lorejoh12 who worked on the DatePicker a lot) should confirm. |
|
🎉This issue was addressed in #18556, which has now been successfully released as Handy links: |
|
🎉This issue was addressed in #18556, which has now been successfully released as Handy links: |
|
🎉This issue was addressed in #18556, which has now been successfully released as Handy links: |
|
🎉This issue was addressed in #18556, which has now been successfully released as Handy links: |
|
🎉This issue was addressed in #18556, which has now been successfully released as Handy links: |
|
🎉This issue was addressed in #18556, which has now been successfully released as Handy links: |
|
🎉This issue was addressed in #18556, which has now been successfully released as Handy links: |
|
🎉This issue was addressed in #18556, which has now been successfully released as Handy links: |
|
🎉This issue was addressed in #18556, which has now been successfully released as Handy links: |
|
🎉This issue was addressed in #18556, which has now been successfully released as Handy links: |
|
🎉This issue was addressed in #18556, which has now been successfully released as Handy links: |
|
🎉This issue was addressed in #18556, which has now been successfully released as Handy links: |
|
🎉This issue was addressed in #18556, which has now been successfully released as Handy links: |
|
🎉This issue was addressed in #18556, which has now been successfully released as Handy links: |
|
🎉This issue was addressed in #18556, which has now been successfully released as Handy links: |
|
🎉This issue was addressed in #18556, which has now been successfully released as Handy links: |
|
🎉This issue was addressed in #18556, which has now been successfully released as Handy links: |
|
🎉This issue was addressed in #18556, which has now been successfully released as Handy links: |
|
🎉This issue was addressed in #18556, which has now been successfully released as Handy links: |
|
🎉This issue was addressed in #18556, which has now been successfully released as Handy links: |
|
🎉This issue was addressed in #18556, which has now been successfully released as Handy links: |
|
🎉This issue was addressed in #18556, which has now been successfully released as Handy links: |
|
🎉This issue was addressed in #18556, which has now been successfully released as Handy links: |
|
🎉This issue was addressed in #18556, which has now been successfully released as Handy links: |
|
🎉This issue was addressed in #18556, which has now been successfully released as Handy links: |
|
🎉This issue was addressed in #18556, which has now been successfully released as Handy links: |
|
🎉This issue was addressed in #18556, which has now been successfully released as Handy links: |
|
I just tested this new component and it's impossible to set default value for the time picker which makes it unusable for any edit form |
|
@yunicz That's a known limitation of the initial implementation. Can you please make a feature request? |
and others
I would like a web implementation of a time picker.
I believe that this would be an expansion of the current web DatePicker as the iOS and Android controls are DateTimePickers.
https://developer.microsoft.com/en-us/fabric#/controls/web/datepicker
No, I have not discussed this with the team.
Additional context/screenshots
https://developer.microsoft.com/en-us/fabric#/controls/ios/date-time-picker
https://developer.microsoft.com/en-us/fabric#/controls/android/date-time-picker
The text was updated successfully, but these errors were encountered: