mirror of
https://github.com/tc39/test262.git
synced 2025-08-22 10:28:30 +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.
21 lines
852 B
JavaScript
21 lines
852 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.now.plaindatetime
|
|
description: Leap second is a valid ISO string for TimeZone
|
|
features: [Temporal]
|
|
---*/
|
|
|
|
let timeZone = "2016-12-31T23:59:60+00:00[UTC]";
|
|
|
|
// A string with a leap second is a valid ISO string, so the following two
|
|
// operations should not throw
|
|
|
|
Temporal.Now.plainDateTime("iso8601", timeZone);
|
|
Temporal.Now.plainDateTime("iso8601", { timeZone });
|
|
|
|
timeZone = "2021-08-19T17:30:45.123456789+23:59[+23:59:60]";
|
|
assert.throws(RangeError, () => Temporal.Now.plainDateTime("iso8601", timeZone), "leap second in time zone name not valid");
|
|
assert.throws(RangeError, () => Temporal.Now.plainDateTime("iso8601", { timeZone }), "leap second in time zone name not valid (nested property)");
|