Last modified: 2014-02-22 21:43:37 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 T28892, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 26892 - Personal list of threads/messages should have a local table of contents.
Personal list of threads/messages should have a local table of contents.
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
LiquidThreads (Other open bugs)
unspecified
All All
: Lowest enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
http://translatewiki.net/w/i.php?titl...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-01-23 17:06 UTC by Purodha Blissenbach
Modified: 2014-02-22 21:43 UTC (History)
4 users (show)

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


Attachments

Description Purodha Blissenbach 2011-01-23 17:06:45 UTC
Each time when I select "mark as read" on a thread on the page "new messaegs (some number)" of my personal user-specific links, the page is redisplayed and both paging and scrolling are started from the newest thread. Since I do not mark newer threads as read before having read then, and I read them in roughly chronologial order, I have to page back to where I was before, then scroll down to where I was before, and continue reading. With several 100 threads and messages, this is extremely time consuming. I spend a magnitude more time waiting for pages to be sent to me just to immediately go to the next page, and scrolling down than actually reading. Unfortunately I do not have a choice to avoid using this extension, else I would.

Thus I suggest to include a table of contents in the personal page, so as to avoid the need of scolling to threads. Since impersonal threaded pages have one already, I believe, this would be pretty easy to do.

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


Navigation
Links