mirror of
https://github.com/tc39/test262.git
synced 2025-07-31 01:44:54 +02:00
Previously, "nested" calendar property bags were unwrapped up to one level. That is, this object: { calendar: { // ...Temporal.Calendar methods } } would not be considered to implement the Calendar protocol, but would have its calendar property used instead, if it were passed to an API that required a Calendar 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
774 B
JavaScript
17 lines
774 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.plaindatetime.compare
|
|
description: Leap second is a valid ISO string for a calendar in a property bag
|
|
features: [Temporal]
|
|
---*/
|
|
|
|
const calendar = "2016-12-31T23:59:60";
|
|
|
|
const arg = { year: 1976, monthCode: "M11", day: 18, calendar };
|
|
const result1 = Temporal.PlainDateTime.compare(arg, new Temporal.PlainDateTime(1976, 11, 18));
|
|
assert.sameValue(result1, 0, "leap second is a valid ISO string for calendar (first argument)");
|
|
const result2 = Temporal.PlainDateTime.compare(new Temporal.PlainDateTime(1976, 11, 18), arg);
|
|
assert.sameValue(result2, 0, "leap second is a valid ISO string for calendar (second argument)");
|