Today, I was wondering, whether the passkey “Created 02/09/2024” is from February or September. To get around this, I usually configure everything to ISO8601, which would be 2024-09-02. Ideally, the browser extension would follow the system locale to resolve this.
Contrary to 24 Hour clock in addition to AM/PM, I see the time in 24h format, so I think there might be some movement already.
I found this feature request while searching for any existing discussions about a similar issue with the Android app (it shows “last update” and “last sync” in a fixed American format, ignoring the system locale). This issue with Passkeys seems to be more of the same.
I’d actually consider this and any other similar mishandling of date formats to be a bug rather than a feature request. It really isn’t acceptable to use the American format anywhere other than on a device that has been set to an American locale - in the eyes of everywhere else in the world, it’s a strange half-reversed format that is almost impossible to parse!
There are several GitHub issues on the topic, as well as comments here in the forums. Would the Bitwarden devs be able to give us an update, and hopefully an ETA for this widespread problem to be fixed system-wide? Provided dates always follow the system locale, it’s less critical for them to be configurable, though that would be great if it’s easy. If for some reason it really has to be a fixed format, ISO8601 is the only viable option.
Thanks!