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

Temporal.now.calendar() ? #873

Closed
justingrant opened this issue Sep 4, 2020 · 3 comments
Closed

Temporal.now.calendar() ? #873

justingrant opened this issue Sep 4, 2020 · 3 comments

Comments

@justingrant
Copy link
Collaborator

My understanding from previous discussions was that we'd decided not to offer a Temporal.now.calendar() because the default calendar wasn't something we could reliably obtain in JavaScript and/or because we felt that the default calendar wouldn't actually represent the user's intent reliably enough. But after this morning's discussion now I'm not sure because there was an assumption that we could use a default locallized calendar in toLocaleString.

Did something change? Or am I misunderstanding the reason why we're not offering Temporal.now.calendar()?

@sffc
Copy link
Collaborator

sffc commented Sep 5, 2020

+1. This is a way for us to expose the identity of the environment-sensitive calendar without relying only on Intl.

@littledan
Copy link
Member

I was imagining that we would focus on exposing the locale through the navigator.locales proposal on the HTML side. Do we need both interfaces?

@ptomato
Copy link
Collaborator

ptomato commented Sep 18, 2020

Meeting, Sept. 18: Due to the concern of "calendar from the locale" not being a reliable or mature way to express the user's actual preference, we will not have this method. See #292.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants