Page MenuHomePhabricator

When a user clicks view message, take user to the subject of the message they received the notification for
Closed, ResolvedPublic

Description

List of steps to reproduce (step by step, including full links if applicable):

  • Trigger a user talkpage notification by having a message posted to a user talk page
  • Check notifications home center
  • Click view message

What happens?:
Presently it takes user to their full user talk page instead of the actual message they received the notification for

What should have happened instead?:

User should be taken to the message they received the notification for

Software version (if not a Wikimedia wiki), browser information, screenshots, other information, etc:

Screenshot_20210711-223847.png (2×1 px, 190 KB)
Screenshot_20210711-223857.png (2×1 px, 158 KB)
Screenshot_20210711-223903.png (2×1 px, 108 KB)

Event Timeline

In this context, after view message was hit, it should've went directly to where it says "oh hey there"

JTannerWMF triaged this task as Medium priority.Jul 11 2021, 9:54 PM

On Beta 2.7.50376 2021-09-27 the behavior has "view message" taking people to the general talk page again

On Beta 2.7.50376 2021-09-27 the behavior has "view message" taking people to the general talk page again

@JTannerWMF What specific notification are you referring to? Is it a notification of the form [user] left a message on your talk page in [some section]? or of the form [user] left a message on your talk page? If it's the latter, then we have no way of knowing which topic to navigate to, so we just show the general talk page.

This one appears to be happening on 2.7.50376-r-2021-09-27

Here is what I am seeing:

This is the notification

Screenshot_20211004-103258.jpg (2×1 px, 595 KB)

Tapping here after tapping the notification
Screenshot_20211004-103305.jpg (2×1 px, 434 KB)

Shows the wrong message (in this case the 1st message in this user's talk page, which I unfortunately titled "talk page". Sorry for any confusion)
Screenshot_20211004-103310.jpg (2×1 px, 302 KB)

This is the message that should be shown
Screenshot_20211004-103316.jpg (2×1 px, 161 KB)

Great catch, @ABorbaWMF !
That's a genuine regression caused by some recent changes to the backend API that we must have missed.
This is now updated in the latest alpha, and will be cherry-picked onto our release.