@Aklapper possibly a result of the MediaViewer error page linking to Phabricator. I wonder if that should be changed to the MediaWiki support page. (Or could make Phabricator show some kind of tutorial when an extra URL parameter is present?)

@Tgr: Uh, wasn't aware of that, thank you.

In T109240#1555134, @Tgr wrote:

@Aklapper possibly a result of the MediaViewer error page linking to Phabricator. I wonder if that should be changed to the MediaWiki support page.

So users are pointed to some random page (either Phabricator or on-wiki) to "report the issue" (without any hints how to do that in an effective way), and without any automatic passing of e.g. the problematic image URL or without showing or even passing any actual error message?
I don't think that helps anybody. Neither reporters nor editors.
Wherever a feedback venue is it should be where someone (developers) actually takes a look (and with (automated?) instructions how to provide sufficient information for developers). But if noone takes a look it does not matter if it's Phabricator or a wiki page (see the depressive UW feedback page example on Commons) and I'd rather disable such feedback links entirely instead of giving users a fake feeling that someone looks at their feedback.

(Or could make Phabricator show some kind of tutorial when an extra URL parameter is present?)

Not that I knew.

In T109240#1556824, @Aklapper wrote:

So users are pointed to some random page (either Phabricator or on-wiki) to "report the issue" (without any hints how to do that in an effective way), and without any automatic passing of e.g. the problematic image URL or without showing or even passing any actual error message?

Pretty much; only the project is prefilled. Providing URL / error/ browser details would be quite easy actually, I'm just not sure if it is acceptable privacy-wise.