# WONTFIX
# The spec calls for higher floating-point division precision than what JS's
# 64-bit floats provide. proposal-temporal/polyfill achieves this via string
# manipulation hacks:
# https://github.com/tc39/proposal-temporal/blob/171f1c3b630f91b1a0bba80ce5cbfcfa5b14c478/polyfill/lib/timeduration.mjs#L92
#
# Our polyfill avoids the associated performance degradation and filesize
# increase by doing simple native JS number division, but this sometimes results
# in less precise results. Example:
#
#   OURS: 816.5692187493501
#   SPEC: 816.56921874935
#
built-ins/Temporal/Duration/prototype/total/precision-exact-mathematical-values-5.js
built-ins/Temporal/Duration/prototype/total/precision-exact-mathematical-values-6.js

# WONTFIX
# We don't implement ChainDateTimeFormat (normative optional), the ES5-era
# compatibility path where calling Intl.DateTimeFormat as a function on a
# DateTimeFormat-shaped receiver initializes that receiver in place, stashing
# the real formatter behind %Intl%.[[FallbackSymbol]] for UnwrapDateTimeFormat
# to find. It exists only to keep pre-class subclassing idioms working, is
# unrelated to Temporal, and a faithful implementation would need a symbol that
# is per-realm and shared with Intl.NumberFormat, which a shell scoped to one
# constructor cannot mint.
intl402/DateTimeFormat/intl-legacy-constructed-symbol-on-unwrap.js
intl402/DateTimeFormat/intl-legacy-constructed-symbol-property.js
intl402/DateTimeFormat/intl-legacy-constructed-symbol.js

# ENV-ISSUE
# Temporal test262 runner does not support $262.createRealm()
intl402/DateTimeFormat/proto-from-ctor-realm.js

# ENV-ISSUE
# https://github.com/tc39/ecma402/issues/402
intl402/DateTimeFormat/prototype/resolvedOptions/hourCycle-default.js

# ENV-ISSUE
# Native Intl.DateTimeFormat's JS-facing format methods accept Date-bounded
# epoch milliseconds. ECMA-402's Temporal bridge instead formats plain Temporal
# objects from internal epoch-nanosecond records, so edge ISO dates must not hit
# Date TimeClip. Our wrapper delegates through epoch milliseconds, so these
# out-of-TimeClip Temporal plain-object cases throw before native Intl can
# produce strings or parts.
intl402/DateTimeFormat/prototype/format/temporal-objects-no-time-clip-non-latin-numerals.js
intl402/DateTimeFormat/prototype/format/temporal-objects-no-time-clip-weekday.js
intl402/DateTimeFormat/prototype/format/temporal-objects-no-time-clip.js
intl402/DateTimeFormat/prototype/formatRange/temporal-objects-no-time-clip-weekday.js
intl402/DateTimeFormat/prototype/formatRange/temporal-objects-no-time-clip.js
intl402/DateTimeFormat/prototype/formatRangeToParts/temporal-objects-no-time-clip-weekday.js
intl402/DateTimeFormat/prototype/formatRangeToParts/temporal-objects-no-time-clip.js
intl402/DateTimeFormat/prototype/formatToParts/temporal-objects-no-time-clip-weekday.js
intl402/DateTimeFormat/prototype/formatToParts/temporal-objects-no-time-clip.js

# ENV-ISSUE
# Native Intl differences around time-zone canonicalization, Unicode-extension
# option resolution, Islamic fallback calendar IDs, and era part strings would
# require a broad DateTimeFormat compatibility shim. Keep these failures unless
# a future fix is small, local, and clearly improves real Temporal behavior.
intl402/DateTimeFormat/canonicalize-timezone.js
intl402/DateTimeFormat/canonicalize-utc-timezone.js
intl402/DateTimeFormat/constructor-options-calendar-islamic-fallback.js
intl402/DateTimeFormat/prototype/formatToParts/era.js
intl402/DateTimeFormat/prototype/resolvedOptions/resolved-calendar-unicode-extensions-and-options.js
intl402/DateTimeFormat/prototype/resolvedOptions/resolved-numbering-system-unicode-extensions-and-options.js
intl402/DateTimeFormat/timezone-legacy-non-iana.js
intl402/DateTimeFormat/timezone-case-insensitive.js
intl402/DateTimeFormat/timezone-not-canonicalized.js

# ENV-ISSUE
# Chinese/Dangi calendar math follows the host ICU data scraped from
# Intl.DateTimeFormat. Current test262 uses ICU4X Chinese calendar data for a
# few cases where Node's ICU4C disagrees, including the 1987 leap-month slot and
# two Chinese new-year boundaries. We intentionally do not patch the scraped
# Intl data for these mismatches; doing so would make Temporal fields diverge
# from DateTimeFormat output in the same runtime.
intl402/Temporal/PlainDate/prototype/daysInYear/basic-chinese.js
intl402/Temporal/PlainDate/prototype/monthCode/chinese-calendar-dates.js
intl402/Temporal/PlainDateTime/prototype/daysInYear/basic-chinese.js
intl402/Temporal/PlainDateTime/prototype/monthCode/chinese-calendar-dates.js
intl402/Temporal/PlainMonthDay/prototype/monthCode/chinese-calendar-dates.js
intl402/Temporal/PlainYearMonth/prototype/daysInYear/basic-chinese.js
intl402/Temporal/PlainYearMonth/prototype/monthCode/chinese-calendar-dates.js
intl402/Temporal/ZonedDateTime/prototype/daysInYear/basic-chinese.js
intl402/Temporal/ZonedDateTime/prototype/monthCode/chinese-calendar-dates.js
