-
Notifications
You must be signed in to change notification settings - Fork 163
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
Integrate with Intl.DurationFormat #452
Comments
We have an open proposal to add Intl.DurationFormat: |
Discussed in the March 19 meeting: We'll update the Intl.DurationFormat in our polyfill to match the one in the proposal as needed. @ryzokuken Should this issue remain open to implement that, or is it more something that will be done on an ongoing basis as other issues are fixed? |
I'm leaving out the Stage 3 milestone; I think the integration at both the spec and polyfill levels are more milestones for Intl.DurationFormat, and don't block Stage 3 or polyfill distribution for Temporal. |
Should implementers go ahead and provide locale-sensitive Maybe there's confusion because the Temporal polyfill already provides locale-sensitive |
Alternatively, maybe the polyfill should remove this behaviour until it has been specified, to avoid causing confusion. @ptomato This is a potential blocker for us to be able to ship Temporal. Would it be possible for the champions to have a look at this and give us some guidance on the best way to proceed? |
So it should be safe to add CC @ryzokuken |
I'll take a look at this next week. |
This operation had a placeholder note until the Intl.DurationFormat proposal would reach stage 4. Now that the proposal is stage 4, we can replace the placeholder note with the real implementation. Closes: #452
@dminor @anba This is done in #3088, which is based on the current stage 4 state of Intl.DurationFormat in tc39/ecma402#943. Hopefully this is what you need! I'd be interested in your opinion on whether it needs to wait for tc39/ecma402#943 before merging or you'd be happy with merging it now. |
This operation had a placeholder note until the Intl.DurationFormat proposal would reach stage 4. Now that the proposal is stage 4, we can replace the placeholder note with the real implementation. Closes: #452
I don't think this needs to wait for tc39/ecma402#943. |
This operation had a placeholder note until the Intl.DurationFormat proposal would reach stage 4. Now that the proposal is stage 4, we can replace the placeholder note with the real implementation. Closes: #452
This operation had a placeholder note until the Intl.DurationFormat proposal would reach stage 4. Now that the proposal is stage 4, we can replace the placeholder note with the real implementation. Closes: #452
#129 (comment) never really took
Duration
into account from what it seems, we should discuss this in a meeting.The text was updated successfully, but these errors were encountered: