Closed Bug 1222292 Opened 9 years ago Closed 9 years ago

[Certificate viewer] SSL certificate details uses ambiguous date format

Categories

(Core Graveyard :: Security: UI, defect)

42 Branch
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 443811

People

(Reporter: u554791, Unassigned)

References

Details

(Whiteboard: [parity-chrome])

Attachments

(2 files)

Attached image firefox.jpg
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:42.0) Gecko/20100101 Firefox/42.0
Build ID: 20151103081951

Steps to reproduce:

Go to any site with ssl. Look for the certificate details. Look at the Period of Validity.


Actual results:

Dates should be in long format or ISO format.


Expected results:

Date are in an ambiguous short format. See attached screenshots comparing chrome and firefox.
Attached image chrome.jpg
Similar issue that cropped up in old versions of Chrome: 

https://code.google.com/p/chromium/issues/detail?id=483357
(In reply to Jerome Leclanche from comment #0)
> Date are in an ambiguous short format.

The only real shortcoming I see here is that time isn't specified. The date format is determined by your system settings. Are you saying that's not the case for you? If so, what Linux distribution and version are you using?
Component: Untriaged → Security: UI
Product: Firefox → Core
Summary: SSL certificate details uses ambiguous date format → [Certificate viewer] SSL certificate details uses ambiguous date format
Whiteboard: [parity-chrome]
Without knowing my locale, tell me this. What is this certificate's validity period?

* 11th June 2015 - 2nd April 2016
* 6th November 2015 - 4th February 2016

You can't. You'd guess right because of context at best. Like I said in the chromium issue, I'm a european who prefers english locales, but that doesn't mean this date format is comfortable to me - nor is it clear. There's quite a bit of discussion there and hopefully enough reasoning to switch to ISO or long form date format, take a look.
Thanks for filing the bug, but switching to long date format has already been done in Bug 443811 for Firefox 43.

For ISO 8601, see Bug 1053679.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: