Last modified: 2013-02-17 08:16:21 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 T31769, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 29769 - LQT should have a "expand all comments/replies" button
LQT should have a "expand all comments/replies" button
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
LiquidThreads (Other open bugs)
unspecified
All All
: Normal normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-07-08 07:13 UTC by p858snake
Modified: 2013-02-17 08:16 UTC (History)
4 users (show)

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


Attachments

Description p858snake 2011-07-08 07:13:50 UTC
Would be handy on "busy" pages such as http://www.mediawiki.org/wiki/Talk:Article_feedback for example.
Comment 1 Helder 2011-07-15 19:53:01 UTC
(In reply to comment #0)
> Would be handy on "busy" pages such as
> http://www.mediawiki.org/wiki/Talk:Article_feedback for example.

Indeed.

Currently, when a discussion page has lots of comments, it is common to find links like "Show 99 replies" all over the talk page. This means that the most relevant comments in a thread (the recent ones) cannot be found through CTRL+F, unless a user expand all topics manually.

So, it would be good idea to provide users some sort of
 "Expand all comments on this page"
link.

PS: I found this bug when I was going to create a new one about this, inspired by the following comment on Village pump:
http://en.wikipedia.org/w/index.php?title=Wikipedia%3AVillage_pump_%28policy%29&action=historysubmit&diff=439667705&oldid=439662404

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


Navigation
Links