You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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()?
The text was updated successfully, but these errors were encountered:
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.
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 intoLocaleString
.Did something change? Or am I misunderstanding the reason why we're not offering Temporal.now.calendar()?
The text was updated successfully, but these errors were encountered: