Here’s another update:
The Chromium fix for this is released on v150, which is in Canary now – I just tested it out and verified it’s fixed by testing these pages in Data Entry, Capture, and the UI library (choose iso8601 as the calendar) with the Canary version of Chrome
v150 with the fix will be released publicly on June 1, at which point this can be fixed by updating browsers to the latest stable version ![]()