Page MenuHomePhabricator

Echo notifications should have a larger clickable surface area
Closed, ResolvedPublic


Screenshot of an individual Echo notification from's Special:Notifications

Echo notifications should have a larger clickable surface area. I'm going to upload a screenshot with comment 0 and expand on my views in comment 1.

Version: unspecified
Severity: normal

Attached: (173×939 px, 21 KB)



Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 1:38 AM
bzimport added a project: Notifications.
bzimport set Reference to bz47665.
bzimport added a subscriber: Unknown Object (MLST).

Looking at attachment 12183, we have three links:

In my mind, the most important link for a notification of this type is the third link (an anchored link to the discussion of which the user was notified). However, in the current design, this link is behind an arrow icon ("→‎"), which I think is fairly obscure.

We should consider making the entire grey box a clickable surface area that links directly to the relevant talk page section. This should be considered for both Special:Notifications and the Echo notifications menu. A larger surface area makes it much easier for users to view what the notification relates to, particularly on touchscreen devices (there's really no chance in hell that I'm going to be able to click the "→‎" link on an iPad).

My recommendation would be to remove the arrow altogether and leave only the section name. I also would leave the other two links and have them take precedence over the larger underlying grey blob link (if that makes sense).

Hi MZ, we would like to get more community feedback on the question of how many links to include in the notifications that appear in the flyout and the archive page. There are good arguments for and against having a single link per notification.

For now, we have implemented it differently on the flyout (only one link) and on the archive page (several links), so that community members can compare these two approaches easily. This is also consistent with the way other top sites like Facebook have solved this issue: on FB, the flyout has a single link, but it has multiple links on their archive page.

This is a tough issue to solve. For experienced users, having multiple links is beneficial, because it gives them more flexibility. For new users, a single link is preferrable, because it doesn't force them to make a decision. Also, for some notifications, it is not always obvious which single link is most useful to all user groups. For example, the Thanks notification takes you to the diff page, but one could make a reasonable argument that linking to the user page of the person who thanked you could lead to a more constructive interaction than just going back to the edit you previously made.

For all those reasons, we would like to punt on this issue, and make a decision in a few weeks, after we've heard from both new and experienced users.

Thanks for your understanding.

I'm not sure that directly addresses the issue MZ is discussing. We actually considered making entire notifications clickable, but since there were other links in the notices, we thought this would be a bit confusing. The alternative idea was to have a prominent button in each notification that links to the most important/logical destination. However since some notifications have two equally important links (or theoretically no links), there isn't any way we could make this make this consistent across all notifications. My personal suggestion for fixing this issue (and several others) would be to have a separate flyout just for talk page notifications (with a separate badge next to 'Talk') and put buttons on them for going directly to the sections.

The items in the flyout are clickable in their entirety.

EBernhardson subscribed.
matmarex updated the task description. (Show Details)

This has been fixed by the "new" Special:Notifications in 2016 (T129176).