Does this issue occur when all extensions are disabled?: Yes
- VS Code Version: Version: 1.78.1
- OS Version: macOS 12.6.3 (21G419)
Steps to Reproduce:
- Set your OS date format to
dd/mm/yyyy.
- Open the Extensions pane.
- Click on an extension.
Expected behaviour
The dates in "More Info" are shown in dd/mm/yyyy format. VSCode should have a setting where the locale can be set, but should use the system locale if it has not been set. (I assume there is no setting; a search for "locale" doesn't find anything, and "date" or "language" produces far too many results to be useful!)
Alternatively, if implementing locale support here is tricky, yyyy-mm-dd could be used — or just text like "July 11, 2016" rather than short dates.
Actual behaviour
The dates are shown in mm/dd/yyyy format, despite the fact that most locales do not use this format.
Here's an example, grabbed today (May 10, 2023). The "last release" and "last updated" dates give a clue in this case, as it's not yet September or October, but the "published" date looks valid. However, it's July 11, 2016 and not November 7, 2016.
Does this issue occur when all extensions are disabled?: Yes
Steps to Reproduce:
dd/mm/yyyy.Expected behaviour
The dates in "More Info" are shown in dd/mm/yyyy format. VSCode should have a setting where the locale can be set, but should use the system locale if it has not been set. (I assume there is no setting; a search for "locale" doesn't find anything, and "date" or "language" produces far too many results to be useful!)
Alternatively, if implementing locale support here is tricky, yyyy-mm-dd could be used — or just text like "July 11, 2016" rather than short dates.
Actual behaviour
The dates are shown in mm/dd/yyyy format, despite the fact that most locales do not use this format.
Here's an example, grabbed today (May 10, 2023). The "last release" and "last updated" dates give a clue in this case, as it's not yet September or October, but the "published" date looks valid. However, it's July 11, 2016 and not November 7, 2016.