Thanks @Paladox - I'll close this now.

I updated PageForms yesterday which brought in some fixes for PageForms.js.

It is now working! I could tell it was going to work because previously it had a processing circle of whirliness in the centre of the screen when you were creating a form and now it doesn't. I haven't closed this ticket. I'm interested as to whether someting happened overnight that sorted Cargo out?

Completely upstream with no dependency on us in any way, task here adds no value.

You should be able to enable them now.

In T3861#76112, @Void wrote:

Task has been resolved upstream for a month.

Correction, Special:ListFiles has been fixed. Is there an upstream task for Extension:Editcount?

it's now resolved, maybe because of upgrading...

Not able to reproduce this bug anywhere.

Now that we have upgraded to MediaWiki 1.32, is this still a problem?

@Corey try looking at the Stewards Noticeboard in the mobile view.

@Corey yes it is

The page is still showing properly for me.

The page is displaying correctly for me.

In T3751#72015, @Xenic wrote:

Is there a way for me to "reset" mobile view?

Seconding MacFan that this still does occur. Appears to be an upstream issue.

Blocked by upstream.

And the 'problem' occurs on Wikipedia too when I edit there in Visual Editor mode.

In T1404#66202, @Paladox wrote:

We should uninstall NativeSvgHandler seeing as that's the problem.

This is an upstream task, which are low prio

Yeah, it looks like it's a PHP 7.x thing, since not all extensions have been upgraded for it.

In T3665#72178, @MacFan4000 wrote:

@AmandaCath we can't change the extension files, so this would have to be reported upstream.

Hi, i reverted https://github.com/miraheze/mw-config/pull/2432/files but never reopened this task so i apologise. private wiki's cannot use restbase yet but it is on upstream list of things to do.

It stil does not work for my (private) jcswiki. What should i do?

Bug report upstream, fix would require no action from us so this task achieves nothing here.

Not sure, but if it hasn’t been already, and we can confirm it’s not a Miraheze issue, it should be ASAP.

Has this been reported upstream?

Likely an extension bug unrelated to Miraheze.