Date format in date editing control does not respect locale settings

cpmcgrath
cpmcgrath
Community Member

When viewing an entry with a date in it, it shows in the correct format - dd/MM/yyyy. You then hit the edit button, and it switches to MM/dd/yyyy.

As a side, the control is very hard to use, as you have to use the popup calendar to navigate to the month you want and select the day. Really, we just want to be able to type 21/02/1992 and be done with it.


1Password Version: 8.10.33
Extension Version: Not Provided
OS Version: Windows 11
Browser: Not Provided

Comments

  • Hello @cpmcgrath! 👋

    I'm sorry that 1Password is showing the wrong date format. This is a known issue that our developers are currently investigating and working to fix in a future version of 1Password.

    Would you mind posting a screenshot of your region, language and date settings from Windows so that I can verify that you're running into this known issue?

    I look forward to hearing from you.

    -Dave

    ref: dev/core/core#8747

  • crazystick
    crazystick
    Community Member

    Same issue on Linux:

    1Password for Linux 8.10.36 (81036046)

    View:

    Edit:

  • @crazystick

    I'm sorry for the inconvenience. Our developers are aware of the issue and I've let them know that you're affected as well.

    -Dave

    ref: dev/core/core#28051

  • GavinT
    GavinT
    Community Member
    edited September 27

    Incorrect behaviour around date format not respecting regional settings as per thread.

    The date appears correct when viewing entries, though it is incorrect when creating new items or editing existing entries.


    System
    MacOS
    Sonama 14.6.1

    1Password for Mac 8.10.44
    81044034 on PRODUCTION Channel

  • @GavinT

    Thank you for the report, I've passed it along to our development team. I'm sorry for the inconvenience and hopefully the issue is resolved in a future update soon.

    -Dave

  • roy_orbison
    roy_orbison
    Community Member

    If 1Pass can't yet format dates based on users' locales, it should at least use the unambiguous ISO format. It still places month before day but everyone knows what's what when you use YYYY-MM-DD. The U.S. is the only country that does this misordered date, and everyone else hates it.

  • @roy_orbison

    1Password should respect the system date format but there are cases where that isn't occurring, such as if you have a different region set from your preferred language, and our development team is actively working on the issue.

    I apologize for the inconvenience. Keep an eye on our release notes which will mention a fix as soon as it is released: https://releases.1password.com/

    -Dave

    ref: dev/core/core#28051

  • roy_orbison
    roy_orbison
    Community Member

    @Dave_1P I get that, but it's still using a poor default. From my logs (that also have the good sense to use ISO dates):

    INFO  2024-11-06T23:07:01.540+00:00 ThreadId(18) [1P:op-localization/src/lib.rs:230] system locale detected as 'en-GB'
    INFO  2024-11-06T23:07:01.543+00:00 ThreadId(18) [1P:op-localization/src/lib.rs:256] selected translations for EN_US based on detected locale en-GB
    

    Even if the locales are improved, it's quite possible there will continue to be edge cases, and in those cases U.S. formats should not be the default. If the translation locale is not an exact match of the system's, it should still fall back to ISO.

  • @roy_orbison

    Thank you for the feedback, I've shared it with the team. 🙂

    -Dave

    ref: PB-44264849