Change 625899 had a related patch set uploaded (by Tchanders; owner: Tchanders):
[mediawiki/extensions/MobileFrontend@master] Display the block reason HTML in the block message drawer

https://gerrit.wikimedia.org/r/625899

Change 625899 merged by jenkins-bot:
[mediawiki/extensions/MobileFrontend@master] Display the block reason HTML in the block message drawer

https://gerrit.wikimedia.org/r/625899

@Tchanders @Niharika Further to what I mentioned in yesterday's standup, just some differences found so far. They don't seem too bad, apart from the first one:

• The mobile block drawer does not support {{mbox}} templates, content gets cut off/obscured. On enwiki, this appears to be used for Tor blocks (https://en.wikipedia.org/wiki/Template:Tor):
  
  Template as it appears in mobile block drawer
  
  Template as it appears in a normal article
  • This seems to be because API:Parse adds <div class="mbox-text-span"> element which is not there when the template is rendered in a normal article (example: https://en.wikipedia.beta.wmflabs.org/w/api.php?action=parse&format=json&formatversion=2&text={{Tor%20prod}}&contentmodel=wikitext). Perhaps API:Parse bug?
• Ordered lists (<ol>) items are not numbered (the same thing might happen for unordered lists, I have not tested)
• <code> blocks are not styled

@dom_walden I agree they don't seem too bad. the first one seems okay in that it at least gives you a partial reason for the block. The problem would be worse if all of the message was cut off/obscured. I guess there will be other templates for which this happens. We can't chase down everyone one of those. Let's file a bug for it and leave it in the backlog for now.

In T261944#6483425, @dom_walden wrote:

• The mobile block drawer does not support {{mbox}} templates, content gets cut off/obscured. On enwiki, this appears to be used for Tor blocks (https://en.wikipedia.org/wiki/Template:Tor)

I've updated {{tor}} to not use {{mbox}}.

In T261944#6496031, @Niharika wrote:

@dom_walden I agree they don't seem too bad. the first one seems okay in that it at least gives you a partial reason for the block. The problem would be worse if all of the message was cut off/obscured. I guess there will be other templates for which this happens. We can't chase down everyone one of those. Let's file a bug for it and leave it in the backlog for now.

OK, thanks. I've raised T264187.

Otherwise, templates seem to be rendered as HTML in block reasons.

So, what before might have looked like:

Now looks like:

There does not seem to be a limit to how long the reason is. For example, I have used block reasons which use 10+ templates in a row and they all appear when you scroll down.

Test devices:

• Firefox mobile emulator
• iPhone 8 (emulated)

In T261944#6496141, @JJMC89 wrote:

I've updated {{tor}} to not use {{mbox}}.

Thanks!

Thanks @dom_walden and @JJMC89!

@Tchanders: Hi, the Due Date set for this open task was two months ago. Can you please either update or reset the Due Date (by clicking Edit Task), or set the status of this task to resolved via the Add Action... → Change Status dropdown in case that this task is done (as the patch is merged)? Thanks.