Page MenuHomePhabricator

Flag talk page feedback in toolbar
Open, NormalPublic


Value proposition

From original task description:

What often happens is that reviewers will put some partial effort into reviewing an article, and the give up after hitting a roadblock and being unsure. An ability to write a comment on the talk page that is automatically flagged by the toolbar if another reviewer loads the page would be ideal.

As part of T207443: Feedback for creator should also be posted to article talk page, the comment in the review field is already posted on the article talk page with a dedicated section heading (Feedback from New Page review process - template/configurable by community?). This task is for flagging the presence on feedback on the talk page in the toolbar.

Acceptance criteria:

  • If a reviewer lands on a page in the feed that has talk page feedback (as provided via T207443), the Info flyout should flag that -


    • Text: Previous reviewers of this article left comments on the talk page. (The words talk page link to the feedback section on the talk page).
  • The text does not show up if there is no prior feedback.


Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes

@Insertcleverphrasehere: Adding PageCuration project tag so this task can be found when looking at PageCuration tasks at . No need to add team tags like Growth-Team; that is up to each team (or automatic filters).

The script could either look for a certain header, or we could have a template {{reviewer comments}} that it searches for. Either way would work.

Niharika renamed this task from Reviewer Notes system in Page Curation Tools: system for reviewers to flag talk page comments on new pages to other reviewers to Flag talk page feedback in toolbar .Jun 19 2019, 7:38 PM
Niharika triaged this task as Normal priority.
Niharika updated the task description. (Show Details)
Niharika added a project: Community-Tech.
Niharika moved this task from Untriaged to To be estimated/discussed on the Community-Tech board.
Niharika renamed this task from Flag talk page feedback in toolbar to [4 hours] Flag talk page feedback in toolbar .Jun 20 2019, 5:47 PM
Niharika added a project: Spike.
Restricted Application changed the subtype of this task from "Task" to "Spike". · View Herald TranscriptJun 20 2019, 5:47 PM

We discussed several ideas in the estimation meeting, including but probably not limited to:

1. Parsing the talk page, looking for the section title (which will probably be something like "Feedback from reviewer" or something)

  • Easy-ish
  • Will usually work because new pages probably don't have much talk page activity


  • It's fragile -- discussion could have been archived, or the title manipulated
  • If we use a community-maintained template for talk page messages, we have to first parse it to know what to look for
  • Possibly slow in some cases

2. New API module called after the message is sent that stores the revision ID as a tag

  • Should be accurate because we store the revision ID and can provide a link to the diff
  • Do not need any knowledge of the community-maintained template for talk page messages
  • No performance impact


  • We have to build a new API module
  • Database storage

Looking into this further, I am going to recommend another approach:

3. Searching history by edit summary

  • Easier than the above two options
  • Less fragile than using regular expressions on the full content
  • Community can still use a customized template for the message. The edit summary will always be the same (or have some aspect to it that's consistent)
  • Faster than parsing wikitext
  • enough that we shouldn't need to pre-store anything
  • We will have the revision ID on hand so we can link to the diff


  • ???

For #3, we will need to introduce a standardized edit summary ("... using Page Curation"), but this trivial to do.

Per our standup, even better:

4. Add a change tag to the edit that adds the message

Same as #3 except faster, more proper, less hacky, etc.

We should tag all edits made using Page Curation. For this ticket, we need only to look for edits with this tag on the talk page, since there aren't any other types of Page Curation edits made on article talk pages.

If it helps it also doesn't need to look beyond the last 500 talk page edits and really I can't actually imagine anything past 50 being useful - if an article is getting that much talkpage attention it's likely going to be patrolled already or else isn't patrolled for some other reason. I would anticipate in the overwhelming number of uses cases this will be one of if not the first edit to the talk page - in most cases wikiproject banners are all that are on a talk page when it is patrolled.

If we go with the revision tag idea, it'd of course only be possible to show talk page feedback added since this new feature becomes active. Is that okay?

@Samwalton9 This is a new capability so there is no existing talk page feedback to show.

Ping @Samwilson - wrong sam pinged before.

aezell added a subscriber: aezell.Jun 28 2019, 2:43 PM

@Samwilson I'm OK with repurposing it as it'll keep all the context in one place.

I'm okay with repurposing as well. Will bring it back for estimation.

Niharika renamed this task from [4 hours] Flag talk page feedback in toolbar to Flag talk page feedback in toolbar .Jul 1 2019, 4:42 PM
Niharika removed MusikAnimal as the assignee of this task.
Niharika moved this task from Untriaged to To be estimated/discussed on the Community-Tech board.
Niharika added a subscriber: MusikAnimal.
Niharika changed the subtype of this task from "Spike" to "Task".Jul 1 2019, 5:39 PM

Change 521445 had a related patch set uploaded (by Samwilson; owner: Samwilson):
[mediawiki/extensions/PageTriage@master] Toolbar notice about talkpage feedback

JTannerWMF moved this task from Inbox to External on the Growth-Team board.Jul 9 2019, 7:22 PM
JTannerWMF added a subscriber: JTannerWMF.

Looks like Community-Tech is working on this

I think the styling of the info flyout has changed a bit since this issue was created. The above patch looks like the following; is it okay?

That looks fine @Samwilson but how does the toolbar indicate that a message has been left?

You mean, like the red number bubble that indicates possible issues? There's nothing like that at the moment.

Some indicator, ideally different from the red bubble with the number of issues, to indicate a talk page message is present would be incredibly useful with this - there aren't always reasons to open that particular panel and so a NPP note could get missed by another reviewer.

Sure thing. We could add an extra badge at the bottom corner, e.g.:

Would that be okay?

That would work well in my opinion. Thanks Sam.

Cool, done.

This is now ready for review.

Maybe the 2nd toolbar badge could be a different colour than red, to distinguish it? Or not. And I don't know about 'T' as the indicator; what should it be?

Could be a Mail icon . I personally don't like having two icons there. It looks cramped and confusing. Not sure what's a better way though.

Could the background of the i change (like the Check changing from grey to green when patrolled) for one of these? Perhaps make the issue change the i to red and then add an icon like @Niharika's mail icon for the message? The background color loses the number of issues present but that seems less important that alerting that there are issues in my thinking.

I think the second icon looks a bit weird, too. Would it make more sense to put this information on the "Mark as reviewed" button/flyout, which eventually will leave feedback on the talk page (T207443) ? That way communication-related stuff is all in one place.

We could also have the badge be a count of talkpage messages, if that's of any use.

Re moving it to the 'mark' flyout: sounds good to me, but there are some situations aren't there in which that icon/flyout isn't shown? Would it be annoying to not have the feedback info visible for those pages?

To maximize the use of this feature I would suggest some visual indicator on the toolbar itself - no clicks or flyouts necessary. I leave it to others to design the best way to do this.

@Prtksxna Your expert design advise is needed on this ticket.

I took @Samwilson's help to understand this navigation a bit better. I now understand that the icon currently represents two states:

Open / closeBooleanBlue / Gray
Possible issuesNumberCount badge

We're proposing to add another —

Comments on the talk pageBoolean???

Is there a possibility of this being a count too?

By adding this information on the icon we might be overloading it with a lot of state. This might be more confusing than helpful (especially for people who don't use it on a regular basis). We should consider carefully if this is necessary. Some possible solutions:

  • Two icons: We could have the option of showing two dots of different colors (without any numbers inside them). We'd be representing the possible issues information as Boolean too in this case.
  • Color: (as suggested by @Barkeep49 above) Use the color of the icon (in the non selected state) to show that there are messages here. This is more ambiguous than the green checkmark because its not obvious what state a colored info icon could represent.
  • New icon: A new icon below the that has a count or a simple red dot badge (based on whether we can get a count of the messages or not)

Is there a possibility of this being a count too?

Yep, it is not too hard to get the count of talk page messages.

This is more ambiguous than the green checkmark because its not obvious what state a colored info icon could represent.

We could add a tooltip containing e.g. "There are 3 talk page messages"

So... who wants to make a decision here? :)

aezell added a subscriber: ifried.Wed, Jul 31, 12:39 PM

Tagging @ifried to get her feedback.

ifried added a comment.EditedThu, Aug 1, 6:11 PM

I prefer the third option outlined by @Prtksxna: A new mail icon below the info icon with a count.

Here's why: This option provides the most information to users, although I understand that it looks a bit cluttered. With the addition of a new icon, users can clearly see that there are messages to check out. By contrast, I think option #1 provides too little information and option #2 is too ambiguous. While we can add a tooltip, I would like to select a solution that doesn't require additional explanation to users. As for the counter, I think that providing more (rather than less) information is a better choice. For example, if there's a large number of talk page messages, I imagine that could be very helpful to know at a quick glance.

@Barkeep49, @Insertcleverphrasehere, and everyone else -- How do you feel about this option?

@ifried Works for me. Thanks for everyone's work on this element of the task.

ifried added a comment.Mon, Aug 5, 8:47 PM

@Barkeep49 -- Thanks for your response!
@Samwilson -- Let's proceed with the following: A new mail icon below the info icon with a count. Thanks!

I've updated it to look like this:

Also changed the message to include the count: "Previous reviewers of this article have left (a comment|x comments) on the [talk page]."

Ready for re-review:

ifried added a comment.Wed, Aug 7, 9:16 PM

Thanks, @Samwilson. The updated version (icon display & message) looks good to me.

Change 521445 merged by jenkins-bot:
[mediawiki/extensions/PageTriage@master] Toolbar notice about talkpage feedback

dom_walden added a subscriber: dom_walden.

When the article's Talk page has an edit(s) with the tag "pagetriage"[1] the mail icon appears in the toolbar, with a count.

I checked that the count was correct (by comparing to the Talk page's revision history).

Revisions that have been undone or hidden are still counted.

If the Talk page is deleted or moved (leaving redirect) then the mail icon no longer appears. I am not sure in what circumstances you would only move an article's Talk page (and not the article itself) and whether, in these circumstances, you would still want the moved Talk page's feedback to be flagged.

The mail icon does not appear for User pages (even if they have edits with the "pagetriage" tag). This makes sense as PageTriage does not support posting feedback for User pages.

I could see no aesthetic issues on Firefox, Chromium, Safari, IE11 and Edge 18.

The only possible UI issue is that clicking the mail icon does not open the "Page info" flyout. You have to click the "i" round button. The mail icon does cover up quite a lot of the button, especially if the count is in the double figures and when the button also has the "Possible issues" count in the top right. See, for example, and below screenshot.


  1. This currently isn't done by the tool itself (until T207443), but can be simulated via the API or running this JS code in the browser
ifried added a comment.EditedTue, Aug 13, 3:54 PM

Thanks for the thorough QA testing, @dom_walden. Also, great point about the possible UI issue (i.e. clicking the mail icon doesn't open the "Page info" flyout). While I don't necessarily see this as a dealbreaker (since the user isn't blocked from accessing the flyout), the combination of blocking so much space & not having any direct functionality (other than informing the user of Talk page updates) is a bit awkward. With that in mind, I have a quick question for you: Does clicking on the other icon (i.e. the count of potential issues) result in opening the "Page Info" flyout? If not, I think the lack of functionality for the lower Talk-related icons is probably fine, since they mirror the behavior of the above icons.

Also, @Prtksxna, what do you think? I know we have had some conversations about the current state of the icon representation, and I would be curious to know your thoughts. Do you think we need to perhaps move the mail + counter icons down a bit (so they block less space)? Thanks!

dom_walden added a comment.EditedTue, Aug 13, 4:24 PM

...Does clicking on the other icon (i.e. the count of potential issues) result in opening the "Page Info" flyout?

No. Both icons currently behave the same.