| browser.js |
|
0 |
| calendar-not-supporting-eras.js |
---
esid: sec-temporal.plaindate.from
description: era and eraYear are ignored (for calendars not using eras)
includes: [temporalHelpers.js]
features: [Temporal]
--- |
1552 |
| canonicalize-calendar.js |
---
esid: sec-temporal.plaindate.from
description: Calendar ID is canonicalized
features: [Temporal]
--- |
686 |
| canonicalize-era-codes.js |
---
esid: sec-temporal.plaindate.from
description: Calendar era code is canonicalized
includes: [temporalHelpers.js]
features: [Temporal]
--- |
1007 |
| infinity-throws-rangeerror.js |
---
description: Throws if eraYear in the property bag is Infinity or -Infinity
esid: sec-temporal.plaindate.from
includes: [compareArray.js, temporalHelpers.js]
features: [Temporal]
--- |
1176 |
| one-of-era-erayear-undefined.js |
---
esid: sec-temporal.plaindate.from
description: >
Throw a TypeError if only one of era/eraYear fields is present (for calendar
using eras)
features: [Temporal]
--- |
787 |
| remapping-era.js |
---
esid: sec-temporal.plaindate.from
description: Test remapping behaviour of regnal eras
info: |
CalendarDateFromFields:
1. Perform ? CalendarResolveFields(_calendar_, _fields_, _date_).
2. Let result be ? CalendarDateToISO(_calendar_, _fields_, _overflow_).
CalendarResolveFields:
When the fields of _fields_ are inconsistent with respect to a non-unset
_fields_.[[Era]], it is recommended that _fields_.[[Era]] and
_fields_.[[EraYear]] be updated to resolve the inconsistency by lenient
interpretation of out-of-bounds values (rather than throwing a *RangeError*),
which is particularly useful for consistent interpretation of dates in
calendars with regnal eras.
includes: [temporalHelpers.js]
features: [Temporal]
--- |
4189 |
| shell.js |
---
description: |
This defines helper objects and functions for testing Temporal.
defines: [TemporalHelpers]
features: [Symbol.species, Symbol.iterator, Temporal]
--- |
47572 |