Last modified: 2011-03-13 18:05: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 T23379, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 21379 - Notification to Special:NewMessages on talk page header change
Notification to Special:NewMessages on talk page header change
Status: RESOLVED WONTFIX
Product: MediaWiki extensions
Classification: Unclassified
LiquidThreads (Other open bugs)
unspecified
All All
: Lowest normal with 1 vote (vote)
: ---
Assigned To: Andrew Garrett
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2009-11-01 22:54 UTC by Siebrand Mazeland
Modified: 2011-03-13 18:05 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Siebrand Mazeland 2009-11-01 22:54:44 UTC 
If someone changes the header of my user talk page, I get notified that I have new messages. This leads to Special:NewMessages, but there is nothing new, as the change on on my user talk page outside the threads.
Comment 1 Andrew Garrett 2010-02-04 01:26:51 UTC 
Do you think we should have notifications for modifications to the header of a user's new messages page?
Comment 2 Siebrand Mazeland 2010-02-04 10:14:58 UTC 
Keeping vandalism in mind, it would be a shame if someone changed a topic to "You are a gorgeous blond!" (even though I'm not) and there would be no easy way to find out he changed it in the respective user's talk namespace.

Also see bug 21586.
Comment 3 Andrew Garrett 2010-06-24 17:42:13 UTC 
It seems more likely that this should be handled with the watchlist.
Comment 4 Siebrand Mazeland 2010-06-24 18:13:41 UTC 
(In reply to comment #3)
> It seems more likely that this should be handled with the watchlist.
I very much disagree. Not sure if this component will get formal usability testing, but I would propose that you discuss this with the Lqt team that has been formed.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links