Last modified: 2014-02-19 22:07:19 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 T63046, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 61046 - Topic comments shown in reverse chronological order from topic history comments
Topic comments shown in reverse chronological order from topic history comments
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Flow (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-02-07 18:42 UTC by Chris McMahon
Modified: 2014-02-19 22:07 UTC (History)
4 users (show)

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


Attachments

Description Chris McMahon 2014-02-07 18:42:38 UTC
Seen on http://en.wikipedia.beta.wmflabs.org/wiki/Talk:Flow_QA

Create a topic
Add 3 comments to the topic
In the Actions menu for the topic, click History
Click "3 comments" to open the collapsed view of comments
Click the "comment" link for the 3rd comment

Resulting view has the green bar on the 1st comment.  Green bar should be on the 3rd comment.
Comment 1 Maryana Pinchuk 2014-02-07 18:58:17 UTC
This is actually the intended behavior – if you hover over the timestamps, you'll see the first 3rd comment in the topic history is the 1st comment in the topic :) 

I can see how it's very confusing, though, that the topic history rollups appear in a different chronological order than the comments in the topic (topic history is most recent at the top, posts in topic are most recent at the bottom of the topic). We should fix that.
Comment 2 Chris McMahon 2014-02-07 19:01:06 UTC
Changed topic to reflect the actual issue

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


Navigation
Links