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.

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

Timer UX #1

Closed
zbraniecki opened this issue Jan 24, 2020 · 4 comments
Closed

Timer UX #1

zbraniecki opened this issue Jan 24, 2020 · 4 comments

Comments

@zbraniecki
Copy link
Member

Is this proposal intended to address all of the uses from the original tc39/ecma402#47 ?

If so, one that is specific but not mentioned in the README yet is the "timer UX" - -00:34:12.230 - this is a format used by video players, audio players, stopwatches, timers etc.

If not, why not?

@sffc
Copy link
Collaborator

sffc commented Jan 24, 2020

I think the Timer UX should absolutely be a goal. Otherwise we can already do most of the proposal with Intl.NumberFormat + Intl.ListFormat.

@younies
Copy link
Member

younies commented Jan 30, 2020

There is one of the Formatting widths can support that (it is more smaller than narrow, I need to check it and I will update this comment. And if there is no any width that supports -00:34:12.230, we can introduce a new width.

@sffc
Copy link
Collaborator

sffc commented Jan 31, 2020

ICU calls it "numeric".

Note how this might play into the logic for suppressing fields, because it definitely doesn't make sense to suppress minutes when you have hours and seconds and you are using numeric format.

@younies
Copy link
Member

younies commented Aug 24, 2020

Yes, we covered it.

@younies younies closed this as completed Aug 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants