Last modified: 2011-03-13 18:06:08 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T12264, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 10264 - Include server time in JS output
Include server time in JS output
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: patch, patch-need-review
Depends on:
  Show dependency treegraph
Reported: 2007-06-14 23:52 UTC by Carl Fürstenberg
Modified: 2011-03-13 18:06 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

example implementation (420 bytes, patch)
2007-06-14 23:52 UTC, Carl Fürstenberg

Description Carl Fürstenberg 2007-06-14 23:52:58 UTC
Created attachment 3769 [details]
example implementation

As not every computer on this planet is synked against the servers I suggest to include the server time in the output. Following patch is an example how to. Though javascript really wants the timestamp in milliseconds, but php's 32 bits wont handle that. But a near second I feel is enough.
Comment 1 Rob Church 2007-06-15 00:24:56 UTC
What for?
Comment 2 Carl Fürstenberg 2007-06-15 00:30:05 UTC
When handling user scripts, it can sometimes be necessary to know if a given comment was posted one minute ago, or 21 minutes ago. As not all computers are synked to the wikipedia servers, it might result in some strange results otherwise (like a comment that is in the future). 
Comment 3 Brion Vibber 2007-06-15 14:10:44 UTC
This is incompatible with caching requirements; cached pages would give the time of the previous page generation, which would just cause weird inconsistent behavior in anything expecting that to be "current" time.

Note You need to log in before you can comment on or make changes to this bug.