Last modified: 2012-11-17 15:33: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 T22103, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 20103 - Add revision count next to "my talk" for unread messages
Add revision count next to "my talk" for unread messages
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
unspecified
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: i18n
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-08-07 07:50 UTC by MZMcBride
Modified: 2012-11-17 15:33 UTC (History)
7 users (show)

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


Attachments

Description MZMcBride 2009-08-07 07:50:24 UTC
Related to bug 12701, the "my talk" link at the top of the page should indicate how many unread messages there are and bold the link if there are unread messages.

This is standard UI for unread messages in every e-mail client or forum software I've used.
Comment 1 Jan Luca 2009-08-08 10:39:45 UTC
See r54628
Comment 2 Brion Vibber 2009-08-10 19:11:42 UTC
Reverted this in r54733; a revision count is not cleanly related to "number of new messages". Recommend waiting until we actually have a sensible message infrastructure such as nicely integrated LiquidThreads.
Comment 3 MZMcBride 2009-10-08 14:19:48 UTC
LiquidThreads has seemingly implemented this in r57515 (bug 20663).
Comment 4 Niklas Laxström 2011-09-20 10:25:37 UTC
Brion: do we want to do this for core at all?
Comment 5 Brion Vibber 2011-09-20 16:00:52 UTC
I'd say this needs to be left to a human-oriented messaging system, so right now that's LiquidThreads and in the future it'll be LiquidThreads' successor (whether that's a cleanup of LQT itself or something new eventually merging into core or something new that stays separate but becomes a shipped-by-default extension).
Comment 6 Nemo 2012-11-17 15:33:09 UTC
(In reply to comment #4)
> Brion: do we want to do this for core at all?

I think this is "fixed" by the Echo extension, although some parts also affect core.
Closing per http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/65116

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


Navigation
Links