1163158 - Use ISO 8601 (YYYY-MM-DD) dates in developer tools

Status: RESOLVED WONTFIX

(DevTools :: Storage Inspector, defect)

Description

[Peter Bengtsson [:peterbe]]

Attachment: Screenshot 2015-05-08 13.42.01.png

Writing dates as 04/05/2015 is ambiguous. Is it 5th of April or 4th of May? Also, a lot of the non-US world uses the 24 clock and if you're not used to seeing the am/pm you might misinterpret the time. 

Using ISO dates (YYYY-MM-DD) is easier to read. Universally accepted and should also contain timezone information.

Comment 1

[Peter Bengtsson [:peterbe]]

Any news on this one?

Comment 2

[Mike Ratcliffe [:miker] [:mratcliffe] [:mikeratcliffe]]

The storage inspector uses GMT as the time format because cookies and other storage types follow the standard of using RFC 1123 dates as the spec dictates. Our tools should follow standards wherever possible.

See https://tools.ietf.org/html/rfc2616#section-3.3.1

3.3.1 Full Date

   HTTP applications have historically allowed three different formats
   for the representation of date/time stamps:

      Sun, 06 Nov 1994 08:49:37 GMT  ; RFC 822, updated by RFC 1123
      Sunday, 06-Nov-94 08:49:37 GMT ; RFC 850, obsoleted by RFC 1036
      Sun Nov  6 08:49:37 1994       ; ANSI C's asctime() format

   The first format is preferred as an Internet standard and represents
   a fixed-length subset of that defined by RFC 1123 [8] (an update to
   RFC 822 [9]). The second format is in common use, but is based on the
   obsolete RFC 850 [12] date format and lacks a four-digit year.
   HTTP/1.1 clients and servers that parse the date value MUST accept
   all three formats (for compatibility with HTTP/1.0), though they MUST
   only generate the RFC 1123 format for representing HTTP-date values
   in header fields. See section 19.3 for further information.