230827 2021-09-27 05:22:11 -0700 REGRESSION (iOS 15): Intl.DateTimeFormat returns 2 digit years when type is 'numeric' 2021-11-23 12:33:22 -0800 1 1 1 Unclassified WebKit JavaScriptCore Other iPhone / iPad Other RESOLVED WORKSFORME https://bugs.webkit.org/show_bug.cgi?id=231545 https://jsfiddle.net/davidwebster/0b6qfu34/5/ InRadar P2 Normal --- 1 davidcwebster ysuzuki blake davidcwebster kevin_neal kontakt matt.carroll139 mmaxfield webkit-bug-importer ysuzuki oldest_to_newest 1797432 0 davidcwebster 2021-09-27 05:22:11 -0700 This bug occurs in Safari on iOS 15. When Intl.DateTimeFormat is formatting a year, and the configuration for year is 'numeric', it returns a two-digit year. However, I expect the full year. Previous versions returned the full year, and other browsers (including Safari 15 on OSX) return the full year. Here's a code sample: const dtf = new Intl.DateTimeFormat('en-AU', { timeZone: 'Australia/Melbourne', year: 'numeric' }); const date = new Date(); const parts = dtf.formatToParts(date); const year = parts.find(part => part.type === 'year') console.log(year.value) // expected output is "2021", but in Safari 15 on iOS, it's "21". You can try this at https://jsfiddle.net/davidwebster/0b6qfu34/5/ 1798365 1 kevin_neal 2021-09-29 09:10:49 -0700 Thank you for filing. What version of iOS 15 are you using? I was not able to reproduce the bug using the latest iOS 15 beta. 1798366 2 webkit-bug-importer 2021-09-29 09:10:57 -0700 <rdar://problem/83673541> 1798707 3 davidcwebster 2021-09-29 17:42:35 -0700 I'm using version 15.0. I'm using the Simulator in XCode because I don't have a real iPhone to test on. I can't find any way to use the latest iOS 15 beta in the simulator. 1799766 4 ysuzuki 2021-10-02 14:10:40 -0700 Thank you for filing an issue! I tried it in iOS 15 device and iOS 15 simulator, but I cannot reproduce this issue. Both shows the "2021", expected behavior. For now, I'll just add that as a regression test. 1799767 5 ysuzuki 2021-10-02 14:24:39 -0700 Committed r283446 (242433@main): <https://commits.webkit.org/242433@main> 1799768 6 ysuzuki 2021-10-02 14:25:24 -0700 Since we cannot reproduce this issue, we didn't change the code, but adding a test case to our stress tests to ensure that this is/will be happening. Thanks. 1801828 7 matt.carroll139 2021-10-07 15:28:19 -0700 Can this please be reopened. It seems the bug still exists. This test case passes: ``` const dtf = new Intl.DateTimeFormat('en-AU', { timeZone: 'Australia/Melbourne', year: 'numeric' }); const date = new Date(2021, 9, 2); const parts = dtf.formatToParts(date); const year = parts.find(part => part.type === 'year') shouldBe(year.value, "2021") ``` This test case will fail: ``` const dtf = new Intl.DateTimeFormat('en-AU', { timeZone: 'Australia/Melbourne', year: 'numeric', month: '2-digit', day: '2-digit' }); const date = new Date(2021, 9, 2); const parts = dtf.formatToParts(date); const year = parts.find(part => part.type === 'year') shouldBe(year.value, "2021") // actual is "21" ``` 1803302 8 ysuzuki 2021-10-12 12:21:42 -0700 (In reply to Matt Carroll from comment #7) > Can this please be reopened. It seems the bug still exists. > > This test case passes: > > ``` > const dtf = new Intl.DateTimeFormat('en-AU', { timeZone: > 'Australia/Melbourne', year: 'numeric' }); > const date = new Date(2021, 9, 2); > const parts = dtf.formatToParts(date); > const year = parts.find(part => part.type === 'year') > shouldBe(year.value, "2021") > ``` > > > This test case will fail: > > ``` > const dtf = new Intl.DateTimeFormat('en-AU', { timeZone: > 'Australia/Melbourne', year: 'numeric', month: '2-digit', day: '2-digit' }); > const date = new Date(2021, 9, 2); > const parts = dtf.formatToParts(date); > const year = parts.find(part => part.type === 'year') > shouldBe(year.value, "2021") // actual is "21" > ``` Thanks. The updated test case can reproduce the issue. This looks like a data problem in AppleICU (not WebKit), and now tracked by AppleICU team at rdar://83597941. So closing this issue since the issue is in system ICU, not in WebKit code. 1803389 9 ysuzuki 2021-10-12 14:28:31 -0700 *** Bug 231545 has been marked as a duplicate of this bug. *** 1803415 10 matt.carroll139 2021-10-12 14:52:27 -0700 Is there an ETA on when this will be fixed in iOS? 1803417 11 mmaxfield 2021-10-12 14:53:39 -0700 (In reply to Matt Carroll from comment #10) > Is there an ETA on when this will be fixed in iOS? Apple does not comment on future products or releases. 1803420 12 matt.carroll139 2021-10-12 14:54:20 -0700 Ok, thank you. 1809516 13 blake 2021-10-27 17:57:40 -0700 Has there been any update on this, we are still experiencing the issue? 1813827 14 blake 2021-11-10 15:56:59 -0800 Hi, this bug has been marked as resolved but we can see the error is still occurring. Is this being investigated further? 1817504 15 kontakt 2021-11-23 12:33:22 -0800 I was also able to reproduce this bug on Safari 15.1 (17612.2.9.1.20) on macOS Monterey. So this is NOT exclusive to iOS.