Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Date Time Picker: Time zones may need to be at a higher granularity than 1 hour #74

Open
atesgoral opened this issue Aug 23, 2016 · 5 comments
Open

Date Time Picker: Time zones may need to be at a higher granularity than 1 hour #74

atesgoral opened this issue Aug 23, 2016 · 5 comments
Milestone
v2.0.0

Comments

@atesgoral
Copy link
Contributor

There are time zones at 30 minutes and even 15 minutes bounds: https://en.wikipedia.org/wiki/List_of_UTC_time_offsets
@osbornm
Copy link
Contributor

osbornm commented Aug 23, 2016

Yup I'd agree, historically we (Tier3 > CTL) have only supported hour break outs but I'm not opposed to adding the additional "missing" ones

@atesgoral
Copy link
Contributor Author

atesgoral commented Aug 23, 2016 •
edited
Loading

With x4 the existing granularity, a different paradigm than a <select> with a ton of options might have to be investigated, too...

@osbornm
Copy link
Contributor

osbornm commented Aug 23, 2016

is it really x4? or are there just a couple? a quickly looking at the list it seems like there would only be 10 maybe 12 more...

@atesgoral
Copy link
Contributor Author

Yeah, it could as well be a heterogenous list of just all existing time zones on the planet.

@osbornm osbornm added this to the v2.0.0 milestone Sep 7, 2016
@osbornm
Copy link
Contributor

osbornm commented Jan 18, 2017

Is there a customer use case for this currently?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v2.0.0
Development

No branches or pull requests
2 participants
@atesgoral @osbornm