Echo notifications should have a larger clickable surface area
OpenPublic

Assigned To
None
Priority
Normal
Author
MZMcBride
Subscribers
EBernhardson, matmarex, MZMcBride and 4 others
Projects
Reference
bz47665
Description

Screenshot of an individual Echo notification from mediawiki.org'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
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=16447

Attached:

bzimport added a project: Echo.Via ConduitNov 22 2014, 1:38 AM
bzimport added a subscriber: wikibugs-l.
bzimport set Reference to bz47665.
MZMcBride created this task.Via LegacyApr 25 2013, 7:41 PM
MZMcBride added a comment.Via ConduitApr 25 2013, 7:50 PM

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).

Fabrice_Florin added a comment.Via ConduitApr 26 2013, 9:40 PM

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.

kaldari added a comment.Via ConduitApr 26 2013, 9:51 PM

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.

Spage added a comment.Via ConduitSep 23 2013, 8:41 PM

Prioritization and scheduling of this bug is tracked on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/205

matmarex added a comment.Via ConduitNov 1 2013, 6:30 PM

The items in the flyout are clickable in their entirety.

werdna removed a subscriber: werdna.Via WebDec 10 2014, 5:02 PM
EBernhardson triaged this task as "Normal" priority.Via WebMon, Mar 2, 6:49 PM
EBernhardson added a subscriber: EBernhardson.

Add Comment

Column Prototype
This is a very early prototype of a persistent column. It is not expected to work yet, and leaving it open will activate other new features which will break things. Press "\" (backslash) on your keyboard to close it now.