mirror of
https://github.com/tc39/test262.git
synced 2025-07-31 01:44:54 +02:00
24def913ec
Previously, "nested" time zone property bags were unwrapped up to one
level. That is, this object:
{
timeZone: {
// ...Temporal.TimeZone methods
}
}
would not be considered to implement the TimeZone protocol, but would have
its timeZone property used instead, if it were passed to an API that
required a TimeZone protocol object.
These nested property bags are no longer supported. Discussion:
https://github.com/tc39/proposal-temporal/issues/2104#issuecomment-1409549753
Corresponding normative PR:
https://github.com/tc39/proposal-temporal/pull/2485
17 lines
703 B
JavaScript
17 lines
703 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 TimeZone
|
|
features: [Temporal]
|
|
---*/
|
|
|
|
let timeZone = "2016-12-31T23:59:60+00:00[UTC]";
|
|
|
|
const result = Temporal.ZonedDateTime.from({ year: 2000, month: 5, day: 2, timeZone });
|
|
assert.sameValue(result.timeZoneId, "UTC", "leap second is a valid ISO string for TimeZone");
|
|
|
|
timeZone = "2021-08-19T17:30:45.123456789+23:59[+23:59:60]";
|
|
assert.throws(RangeError, () => Temporal.ZonedDateTime.from({ year: 2000, month: 5, day: 2, timeZone }), "leap second in time zone name not valid");
|