Last modified: 2012-03-05 22:53:39 UTC
The "Date" column in Special:Code (e.g., <https://www.mediawiki.org/w/index.php?limit=500&title=Special%3ACode%2FMediaWiki%2Fauthor%2Fsimetrical&offset=71173>) should be big endian. Having the time first (i.e., "01:16, 15 January 2010") is completely useless when you're sorting a multi-year contribution set. You have to read backward, which is silly.
It should also probably be "Date (UTC)" (if it's in UTC, I assume it is) for clarity, but this isn't as important.
Dates and times are shown in the user's selected timezone, so labeling as UTC would be rather incorrect. I'm not sure what is being requested exactly though; are you requesting the ability to sort by timestamp in these views? It doesn't appear to currently be possible, so changing the order of the time and date within the view doesn't appear like it would accomplish much.
(In reply to comment #2) > Dates and times are shown in the user's selected timezone, so labeling as UTC > would be rather incorrect. Incorrect labels would be bad, sure. But for anonymous users, they'd presumably see "Date (UTC)" in the header. If you're logged in, you would see "Date (EST)" or "Date (EET)" or whatever's appropriate. > I'm not sure what is being requested exactly though; are you requesting the > ability to sort by timestamp in these views? It doesn't appear to currently be > possible, so changing the order of the time and date within the view doesn't > appear like it would accomplish much. I keep my monitor pretty zoomed in. I'll attach a screenshot to show what I mean.
Created attachment 10180 [details] Screenshot of Special:Code spanning multiple years As you can see in this screenshot, the date column becomes completely useless. The user is required to read the column backward when scanning across contributions that span multiple years. It would make far more sense to present the information with the biggest values (year) first and then end with the less important part of the date (e.g., the time). I realize that core MediaWiki also presents in this format, but that's a separate issue.
