Page MenuHomePhabricator

Suppress "Your topic was added." toast when first-run experience is visible
Open, Needs TriagePublic

Description

This task involves the work with suppressing the " Your topic was added." and " Your comment was published." toasts when the Automatic Topic Subscriptions first-run experience (T262103) is being displayed.

Background

T262103 introduced a dialog that appears the first time someone becomes automatically subscribed to a discussion they start or comment in.

This means, that in the moment that immediately follows someone starting a new discussion or commenting in an existing discussion on desktop, the interface is trying to simultaneously communicate two things to them in three ways:

MessageCommunication Strategy
The discussion or comment they just attempted to publish has, in fact, been published successfully1) The newly-published discussion or comment is highlighted in yellow and 2) A " Your topic was added." or " Your comment was published." toast appears at the top of the page
They will automatically be notified when new comments are posted in the discussion they just started or commented in3) First-run experience dialog appears atop the newly-published discussion

This screenshot visualizes the above:

Screen Shot 2021-11-30 at 3.32.23 PM.png (1×1 px, 370 KB)

Behavior

  1. Visit a wiki where Automatic Topic Subscriptions are available
  2. Ensure the Automatically subscribe to topics setting within Special:Preferences#mw-prefsection-editing is enabled
  3. Visit a talk page
  4. Publish a comment or start a new discussion

Current

  1. Upon doing so, notice the following appear/happen: i) A toast appears at the top of the page, ii) the discussion you started or comment you published is highlighted momentarily, iii) the You have been subscribed dialog appears

Desired

  1. ✅ Upon doing so, notice the following appear/happen: i) the discussion you started or comment you published is highlighted momentarily, ii) the`You have been subscribed` dialog appears

Event Timeline

the interface is trying to simultaneously communicate two things to them in three ways:

Is this much worse that trying to communicate one thing in two ways (which happen when there is no auto-sub popup)?

I'm also not sure what we are worried about happening here. The post-edit notifications will disappear after a short while, leaving just the auto-sub notification which they have to dismiss manually, so there is not chance of them not seeing that notification.

Yes there's a bit more going on that usual, but it's only once and it is at least consistent.

I agree with Ed that this seems like a non-issue -- it's a one off, with two messages communicating different things in different areas.

ppelberg moved this task from Incoming to Design Review on the Editing-team (Kanban Board) board.

(I'm assigning this task over to @iamjessklein to express an opinion on this ticket.)

Do we know if this is problematic for contributors? We could test if the multiple notifications are getting in the way of the messaging, when we test the auto-subscription workflow. If it is an issue, then we have options:

  1. Suppress the confirmation message and issue a distinct pop-up for first run experiences.
  2. Sequence the timing of the pop-up to appear just slightly after the confirmation message disappears.
  3. Do nothing.

The screenshot actually doesn't completely represent reality because you are missing the element of time here. What happens is that the confirmation message shows briefly with a text highlight and then they both disappear. Meanwhile the pop-up is maintained on screen until it's dismissed.

I would experiment with option 1 if this is a usability issue.