Firefox nonconformances: two bugs around extreme dates. one around toLocaleString dateStyle formatting in Temporal. In Intl Era, CLDR bug around islamic calendar era names, and bug around East Asian lunisolar reference years Chrome nonconformances: one bug on rounding, one around extreme dates, one on parsing allowing >9 decimal places. a couple around toLocaleString formatting in Temporal. on Intl Era, same CLDR bug, and islamic fallback not handled properly
npx test262-harness --hostType=sm --hostPath=$HOME/.esvu/bin/sm -f Temporal --fe Intl.Era-monthcode "test/**/*.js" npx test262-harness --hostType=sm --hostPath=$HOME/.esvu/bin/sm -f Intl.Era-monthcode "test/**/*.js" npx test262-harness --hostType=v8 --hostPath=$HOME/.esvu/bin/v8 -f Temporal --fe Intl.Era-monthcode -- "test/**/*.js" npx test262-harness --hostType=v8 --hostPath=$HOME/.esvu/bin/v8 -f Intl.Era-monthcode -- "test/**/*.js" npx test262-harness --hostType=libjs --hostPath=$HOME/.esvu/bin/ladybird-js -f Temporal --fe Intl.Era-monthcode --hostArgs=--use-test262-global -- "test/**/*.js" npx test262-harness --hostType=libjs --hostPath=$HOME/.esvu/bin/ladybird-js -f Intl.Era-monthcode --hostArgs=--use-test262-global -- "test/**/*.js" npx test262-harness --hostType=graaljs --hostPath=$HOME/.esvu/bin/graaljs-nightly -f Temporal --fe Intl.Era-monthcode --hostArgs='--experimental-options --js.temporal' -- "test/**/*.js" npx test262-harness --hostType=graaljs --hostPath=$HOME/.esvu/bin/graaljs-nightly -f Intl.Era-monthcode --hostArgs='--experimental-options --js.temporal' -- "test/**/*.js" npx test262-harness --hostType=jsc --hostPath=$HOME/.esvu/bin/jsc -f Temporal --fe Intl.Era-monthcode --hostArgs=--useTemporal=1 -- "test/**/*.js" npx test262-harness --hostType=jsc --hostPath=$HOME/.esvu/bin/jsc -f Intl.Era-monthcode --hostArgs=--useTemporal=1 -- "test/**/*.js" npx test262-harness --hostType=boa --hostPath=$HOME/.esvu/bin/boa-nightly -f Temporal --fe Intl.Era-monthcode -- "test/**/*.js" # requires https://github.com/tc39/eshost/pull/147 and https://github.com/devsnek/esvu/pull/66 npx test262-harness --hostType=boa --hostPath=$HOME/.esvu/bin/boa-nightly -f Intl.Era-monthcode -- "test/**/*.js" npx test262-harness --hostType=kiesel --hostPath=$HOME/.esvu/bin/kiesel-nightly -f Temporal --fe Intl.Era-monthcode -- "test/**/*.js" npx test262-harness --hostType=kiesel --hostPath=$HOME/.esvu/bin/kiesel-nightly -f Intl.Era-monthcode -- "test/**/*.js" npx test262-harness --hostType=node --hostPath=$(which node) -f Temporal --hostArgs=... -- "test/**/*.js" npx test262-harness --hostType=hermes --hostPath=$(which deno) -f Temporal --hostArgs='run --unstable-temporal --v8-flags=--expose-gc' -- "test/**/*.js"
e.g., `epochMicroseconds` and `Array.sumPrecise` are not fundamentally different An analogy could be the relatively recent decision to have a separate TG for Source Maps, which made sense because: * There was a whole new domain that needed better specification * There was needed coordination with many tools vendors who don't normally participate on TG1 * There were fundamental questions about scope The same could have been said about Temporal in 2018, but not anymore. There's no major blank space in the date/time domain remaining that's not covered with APIs. We did string serialization. We did time zones. We did calendars. We did arithmetic. We did a tree of interrelated types. There's no needed external specifications required now that RFC 9557 is ratified. And so on. We had a big job to do, we did it, and now it's time to handle off incremental work to well-established TG1/TG2 committees with well-established processes for handling incremental language changes.