Last modified: 2014-11-17 10:34:51 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 T23759, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 21759 - LiquidThreads should allow "mark unread"
LiquidThreads should allow "mark unread"
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
LiquidThreads (Other open bugs)
unspecified
All All
: Normal enhancement with 2 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: 39480
  Show dependency treegraph
 
Reported: 2009-12-04 09:48 UTC by Siebrand Mazeland
Modified: 2014-11-17 10:34 UTC (History)
5 users (show)

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


Attachments

Description Siebrand Mazeland 2009-12-04 09:48:57 UTC
This is a feature request that has a little to do with workflow.

In my e-mail box, I both mark messages for follow-up, but often I quickly scan a message and then mark it unread again for later follow-up.

After working with Lqt for a few weeks, I rarely visit talk pages anymore. Anything I want to see from my watchlist will just be on Special:NewMessages. If I have read the new contribs to a thread** I just mark it read, and it's gone until there is new activity in it.

But if I do come across an interesting topic on a non-watched page, I would like to be able to put that thread on my NewMessages page to later reading (and not only get updates from then on). I think this is not possible with the current version (or is it?).

** hmm, thinking of it, I cannot see which posts are new and which I have read - might be nice to visually indicate that (with a style?)
Comment 1 Brandon Harris 2010-09-09 22:21:46 UTC
Taking this, as it's a design issue at this point.
Comment 2 Andre Klapper 2013-01-09 13:24:52 UTC
Brandon:
This report has been in ASSIGNED status for more than one year and you are set as its assignee. In case that you are not actively working on a fix, please reset the bug status to NEW/UNCONFIRMED.
In case you do not plan to work on a fix in the near future: Please also edit the "Assigned To" field by clicking "Reset Assignee to default", in order to not prevent potential contributors from working on a fix. Thanks for your help!
[assigned>=1y]

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


Navigation
Links