Frank Yung-Fong Tang
Frank Yung-Fong Tang
Currently in ECMA402, each Intl object only listen to a restricted set of U extension specified in "[[RelevantExtensionKeys]] internal slot" and all others are stripped out while constructing the object...
> CC @FrankYFTang -- can you review this proposed change from @longlho and comment on whether it would impact implementations like V8? I believe this is editorial and has no...
@anba could you also take a look at this?
How about this? ``` locale = "en"; opt = { style: "currency", currency: "TWD", timeZone: "Asia/Taipei", dateStyle: "long", listStyle: "short", type: "conjunction" }; [new Date(), 1234, 567, new Date()].toLocaleString(locale, opt)...
We discuss this in TG2 today (2021-11-04). I feel it might be an issue much more complicated than I expected and would like to park this issue and let other...
@sffc @anba @zbraniecki @littledan @rkirsling @gibson042
> 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...
> This sounds like something for DisplayNames, no? First of all, the reason I raise this is not just for the functionality, but for the coherence / consistency of the...
PR is already reviewed in https://github.com/tc39/ecma402/pull/647
not sure. I think what you saw in Node 12 is a bug.