Last modified: 2014-09-13 23:34:09 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 T70136, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 68136 - Flow: Timestamps for new posts, often show "negative seconds ago", at first
Flow: Timestamps for new posts, often show "negative seconds ago", at first
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Flow (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-07-17 06:16 UTC by Quiddity
Modified: 2014-09-13 23:34 UTC (History)
6 users (show)

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


Attachments
screenshot (202.67 KB, image/png)
2014-07-17 06:16 UTC, Quiddity
Details

Description Quiddity 2014-07-17 06:16:01 UTC
Created attachment 15956 [details]
screenshot

When I hit reply on a new post, I often see a negative time for when I posted it, which steadily ticks down to zero, and then starts counting upwards normally. (See screenshot.)  I've seen it as high as "-24 seconds ago".

1) negative time is badly confusing, and should be displayed to the user. Perhaps "in the last few seconds", or "very recently", or "within the last minute".

2) it might be good to also understand what is causing this issue in the first place
Comment 1 Danny Horn 2014-07-18 20:12:07 UTC
In backlog: https://trello.com/c/88HtJH3S
Comment 2 se4598 2014-09-13 23:34:09 UTC
> 2) it might be good to also understand what is causing this issue in the
> first place

I think that the time difference displayed is calculated based on the browser/pc clock, which was/is/can be a bit off compared to the server one (providing the timestamp).
I just had that too, and based on a atom clock website, my clock is currently 25 seconds in the past, which would match, what I saw on my flow post.

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


Navigation
Links