Timothy Flynn ae2acc8cdf LibJS+LibUnicode: Generate a set of default DateTimeFormat patterns ... This isn't called out in TR-35, but before ICU even looks at CLDR data, it adds a hard-coded set of default patterns to each locale's calendar. It has done this since 2006 when its DateTimeFormat feature was first created. Several test262 tests depend on this, which under ECMA-402, falls into "implementation defined" behavior. For compatibility, we can do the same in LibUnicode.		2022-07-22 23:51:56 +01:00
..
DateTimeFormat.@@toStringTag.js	LibJS: Implement a nearly empty Intl.DateTimeFormat object	2021-11-29 22:48:46 +00:00
DateTimeFormat.js	LibJS: Implement the Extend TimeZoneName Option Proposal	2022-01-03 15:11:59 +01:00
DateTimeFormat.prototype.format.js	LibJS+LibUnicode: Generate a set of default DateTimeFormat patterns	2022-07-22 23:51:56 +01:00
DateTimeFormat.prototype.formatRange.js	LibJS: Change test conditions to pass in all time zones	2022-01-21 19:14:38 +00:00
DateTimeFormat.prototype.formatRangeToParts.js	LibJS: Change test conditions to pass in all time zones	2022-01-21 19:14:38 +00:00
DateTimeFormat.prototype.formatToParts.js	LibJS: Change test conditions to pass in all time zones	2022-01-21 19:14:38 +00:00
DateTimeFormat.prototype.resolvedOptions.js	LibJS: Allow specifying keyword values not directly defined for a locale	2022-07-15 12:31:43 +02:00
DateTimeFormat.supportedLocalesOf.js	LibJS: Implement Intl.DateTimeFormat.supportedLocalesOf	2021-11-29 22:48:46 +00:00