Page MenuHomePhabricator

Unable to use links (and all other wikitext) for moderation reasons
Closed, DuplicatePublic

Description

Per T95174, moderation reason fields do not support wikitext. This breaks user expectations and make the explanations less useful than they should be:

Event Timeline

He7d3r created this task.Apr 8 2015, 5:47 PM
He7d3r updated the task description. (Show Details)
He7d3r raised the priority of this task from to Needs Triage.
He7d3r added a subscriber: He7d3r.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 8 2015, 5:48 PM

Hi @He7d3r. Please associate a project with this task, otherwise nobody can find this task when searching in the corresponding project(s) Thanks.

Restricted Application added a project: Collaboration-Team-Triage. · View Herald TranscriptApr 9 2015, 7:56 AM
He7d3r added a comment.Apr 9 2015, 2:15 PM

Wasn't it under Flow already?

He7d3r updated the task description. (Show Details)Apr 9 2015, 3:14 PM
He7d3r set Security to None.
DannyH triaged this task as Normal priority.Apr 9 2015, 4:16 PM
DannyH moved this task from Untriaged to Product/Design Work on the Collaboration-Team-Triage board.
DannyH added a subscriber: DannyH.
Mattflaschen-WMF renamed this task from Unable to use links when explaining why we are hiding a Flow topic to Unable to use links (and other wikitext) for moderation reasons.Apr 23 2015, 1:18 AM
Mattflaschen-WMF updated the task description. (Show Details)
He7d3r updated the task description. (Show Details)Apr 23 2015, 1:53 PM
Mattflaschen-WMF reopened this task as Open.Jun 9 2015, 8:48 PM
Mattflaschen-WMF renamed this task from Unable to use links (and other wikitext) for moderation reasons to Unable to use links (and all other wikitext) for moderation reasons.Nov 25 2015, 1:48 AM

I'll merge this back as a duplicate, on the assumption that @He7d3r just wants the limited (standard) edit-summary parser, and not the full parser (as I think Matt was broadly-interpreting "and other wikitext" to mean).
Re-open, if I was wrong. :-)

@Quiddity: Kind of. But there are cases like this on pages about technical matters:
https://pt.wikipedia.org/w/index.php?diff=40212216&oldid=40199375

== {{t1|SomeTemplate}} ==
Question about the template...

@He7d3r Nod.
But running the full parser on edit summaries (i.e. both standard edit summaries, and/or Flow moderation edit summaries) would be a drastic change, and would require a whole bunch more complexity (e.g. having to sanitize interlanguage links and category links and embedded images, etc). If that were to happen, it should probably be done for all edit-summaries.
Whereas implementing the existing limited-edit-summary-parser for Flow moderation edits, would be a lot easier and just bring consistency.

(I've suggested before, that we could perhaps add a few more elements, to the list of things that the limited-edit-summary-parser can handle, and I think that's probably the best way to add any more functionality. I'm not sure if template expansion (i.e. your example) would be feasible though - too many ways it could go wrong! I've started a tracking task at T119681 and will fill it out once Phabricator stops being problematic)