mirror of
https://github.com/tc39/test262.git
synced 2025-08-24 19:38:33 +02:00
078f3e22a4
Everywhere an ISO string is accepted in Temporal, a seconds value of :60 should always be coerced to :59, because of how leap seconds are handled in ISO strings. In property bags, a 'seconds: 60' property is not subject to that rule: it should be handled according to the overflow option if there is one. These tests existed already for some types; regularize them and add the ones that didn't exist yet.
28 lines
868 B
JavaScript
28 lines
868 B
JavaScript
// Copyright (C) 2022 Igalia, S.L. All rights reserved.
|
|
// This code is governed by the BSD license found in the LICENSE file.
|
|
|
|
/*---
|
|
esid: sec-temporal.zoneddatetime.from
|
|
description: Leap second is a valid ISO string for a calendar in a property bag
|
|
features: [Temporal]
|
|
---*/
|
|
|
|
const timeZone = new Temporal.TimeZone("UTC");
|
|
const calendar = "2016-12-31T23:59:60+00:00[UTC]";
|
|
|
|
let arg = { year: 1970, monthCode: "M01", day: 1, timeZone, calendar };
|
|
const result1 = Temporal.ZonedDateTime.from(arg);
|
|
assert.sameValue(
|
|
result1.calendar.id,
|
|
"iso8601",
|
|
"leap second is a valid ISO string for calendar"
|
|
);
|
|
|
|
arg = { year: 1970, monthCode: "M01", day: 1, timeZone, calendar: { calendar } };
|
|
const result2 = Temporal.ZonedDateTime.from(arg);
|
|
assert.sameValue(
|
|
result2.calendar.id,
|
|
"iso8601",
|
|
"leap second is a valid ISO string for calendar (nested property)"
|
|
);
|