André Bargull

> Note: although the spec currently says that the options should be passed down verbatim, it seems that web reality at least in Chrome 80 is that we don't actually...

A workaround to get the time zone resp. era name is to invoke `formatToParts`: ```js js> new Intl.DateTimeFormat("en", {timeZoneName:"long"}).formatToParts().filter(({type}) => type === "timeZoneName")[0].value "Pacific Daylight Time" js> new Intl.DateTimeFormat("en", {era:"long"}).formatToParts().filter(({type})...

CLDR doesn't seem to provide standalone formats for time zone resp. era in [<availableFormats>](https://github.com/unicode-org/cldr/blob/a3c595342cf324e262b2b7958b7c19028769777b/common/main/en.xml#L2348-L2397). (I'm not even sure there's an explicit standalone support for era and time zones at all...

We seem to go round in circles, special casing `Object.keys` isn't enough to cover all cases. If I had to guess I'd say `[[Get]]` needs to be changed to return...

SpiderMonkey and V8 both seem to respect the `usage` option. ```js js> ["AE", "Ä"].sort(new Intl.Collator("de", {usage: "sort"}).compare) ["\xC4", "AE"] js> ["AE", "Ä"].sort(new Intl.Collator("de", {usage: "search"}).compare) ["AE", "\xC4"] d8> ["AE", "Ä"].sort(new...

I guess "search" (and "standard") were banned from "co" to force users to use the "usage" option instead. (IIRC there are somewhere notes explaining the motivation for the "usage" option...

https://norbertlindenberg.com/2012/12/ecmascript-internationalization-api/index.html confirms that this is the reason why "co" doesn't allow "search" and "standard". Link to meeting notes where "usage" was added: https://docs.google.com/document/d/1-NytPBbsO7dLvt0C2psJkF1Wtt3QdKF3NQAHksF5fyc/edit?hl=ko Plus https://docs.google.com/document/d/1jCoJ7NU8JDTkBKPCDrSpdCVGd8DTl50iVwXvVhhC21s/edit?hl=sr

> Be aware that DefaultLocale may also have -u-nu. _DefaultLocale_ doesn't contain any Unicode extensions per the definition in : > Language tags on the list must not have a...

> Could we change the spec text to CreateDataPropertyOrThrow in the !needsDefaults case for each property we find? I don't understand how this'll prevent the assertion error in Chakra. Can...

Hmm, I don't see an easy way to untangle this, because `ToDateTimeOptions` is also used in `Date.prototype.toLocale[Date,Time]String()` to pre-process the `options` argument. Short of changing `Date.prototype.toLocale[Date,Time]String()` to skip the constructor...