Last modified: 2014-01-23 21:12:26 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 T58475, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 56475 - Echo: The "You have new messages" link should go to a diff and/or subsection
Echo: The "You have new messages" link should go to a diff and/or subsection
Status: PATCH_TO_REVIEW
Product: MediaWiki extensions
Classification: Unclassified
Echo (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Aude
: design
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-01 17:14 UTC by Quiddity
Modified: 2014-01-23 21:12 UTC (History)
7 users (show)

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


Attachments

Description Quiddity 2013-11-01 17:14:02 UTC
The orange "You have new messages" talkpage-message Notification, currently leads just to the top of the user talkpage. (Ie. [User talk:Quiddity])

It should lead to either:
* the subsection (if known, and if there's just one new message), or 
* to the diff (if subsection is unknown, or if there are multiple new talkpage messages).

One user has requested that it *always* lead to the diff, which /would/ be more consistent, but I also understand the desire to not confront everyone with a diff (VE, newcomer friendliness, etcetc). ( https://en.wikipedia.org/wiki/Wikipedia_talk:Notifications#Two_clicks_instead_of_one:_Why.3F )
Comment 1 spage 2013-11-04 18:21:54 UTC
The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/395, but people from the community are welcome to contribute here and in Gerrit.
Comment 2 Kunal Mehta (Legoktm) 2013-11-13 04:23:00 UTC
(In reply to comment #0)
> The orange "You have new messages" talkpage-message Notification, currently
> leads just to the top of the user talkpage. (Ie. [User talk:Quiddity])

This is one of the things I probably miss the most about the OBOD, that I could get a direct diff to the new edits.

> 
> It should lead to either:
> * the subsection (if known, and if there's just one new message), or 
> * to the diff (if subsection is unknown, or if there are multiple new
> talkpage
> messages).

From a code standpoint, either of these are probably doable.

> 
> One user has requested that it *always* lead to the diff, which /would/ be
> more
> consistent, but I also understand the desire to not confront everyone with a
> diff (VE, newcomer friendliness, etcetc).

I don't think always going to the diff is a good idea, for some of the reasons you mentioned.

Adding a "You have new messages (diff)" thing to the personal tools menu would be icky and add some more clutter. I don't know where else we could add the link.

CC'ing Jared for some design input.
Comment 3 MZMcBride 2013-11-13 05:27:50 UTC
I could have sworn this was a duplicate bug... I may be remembering the bug about the Echo drop-down nav thing not including a "view changes" link.
Comment 4 Quiddity 2013-11-13 05:33:31 UTC
(In reply to comment #3)
> I could have sworn this was a duplicate bug... I may be remembering the bug
> about the Echo drop-down nav thing not including a "view changes" link.

You're probably thinking of bug 54391 - which I've been told is just to do with the email bundled diff (or something).
Comment 5 Gerrit Notification Bot 2013-11-13 05:40:29 UTC
Change 94506 had a related patch set (by Aude) published:
Link "You have new messages" to user talk diff

https://gerrit.wikimedia.org/r/94506
Comment 6 Gerrit Notification Bot 2014-01-23 21:12:26 UTC
Change 94506 abandoned by Aude:
Link "You have new messages" to user talk diff

Reason:
since ext.echo.alert.js is deleted, shall try new approach :)

https://gerrit.wikimedia.org/r/94506

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


Navigation
Links