Here we see some languages require moving the mouse over each one to distinguish one from another.
And for other languages even that isn't enough.

I would love to upload a screenshot, but due to bugs with phabricator, that will have to wait until I walk over the hill tomorrow to the high-speed Network.

In our mobile browser if we go into settings and click desktop view, we see what the problem originates from. Apparently we are seeing the last three items in each table row: the picture, what it was uploaded by, and the current status: if it is a current picture it is "yes".

OK that is good to know. But those valid uses all fall into the expert-user category.
For the general public: they need the handholding version.

OK, I created [[T293059]].

Holy smokes,

Certainly today is the first time anybody thought about it!

1. Add button to HTML mail: [Report]

There is a horizontal scroll bar. One would expect it to operate on the full width. There are no other tables or content to the right or left.

So finer grained control of what to show is needed.

Incompatible with current MediaWiki.

In fact, on e.g., Miraheze, the User creation log, and User rename log, have made a total trash dump of Recent Changes.
There should be a way for admins to be able to keep them out of Recent Changes by default.
Perhaps they should be in a separate Recent Changes for Power Users / Admins.

List of steps to reproduce (step by step, including full links if applicable):

• Use a real cell phone.
• Visit https://en.m.wikipedia.org/
• Tap the magnifying glass.

Yes.
Even https://commons.wikimedia.org/w/index.php?title=Special:Search
cannot search for 'Files/Images uploaded by Jidanni with "seeds" in the title'.
Therefore on https://commons.wikimedia.org/w/index.php?title=Special:ListFiles/Jidanni&ilshowall=1 ,

I am saying, here the user is looking at
https://commons.wikimedia.org/w/index.php?title=Special:ListFiles/Jidanni&ilshowall=1
and is wondering 'Where is that picture with "Seeds" in the title, that I remember I uploaded?'

(I was worried that it was "not a bug" so didn't select the bug template.)

Also only showing users %PERCENT%ENCODED%MESS puts them at a disadvantage of their U.S. ASCII friends.
Yes, that is the only way to guarantee a link will work,
but, maybe, it is time to just use the raw UTF-8. I bet most mail readers can deal with it.

Your screenshot cuts off the vital ends of lines, so we cannot see if your parser is linking to
https://zh.wikipedia.org/wiki/%E7%A9%8D%E4%B8%B9%E5%B0%BC vs.
https://zh.wikipedia.org/wiki/%E7%A9%8D%E4%B8%B9%E5%B0%BC查看当前版本

Ah, but when will gluing URLs to what follows fail:
Always.

If there is there was a space already in front of $1 (i.e., $1 includes a space built in) as you say(?), then preceding words wouldn't get glued tohttps://example.com .
Same if there was a space at the end, then https://example.comwouldn't get glued to the following word.

要查看此次更改，请参见$1

Maybe if the $1 (itself) contained a space in the front and back of it, it would magically solve the problem for all 256 etc. languages (multiplied by five or six form items. We're talking about thousands of problems solved!. (At the price of not being able to occasionally glue things together.))
Of course a second compressor program needs to come along and reduce any multiple spaces back to a single one.

Currently if the user replaces a paragraph with ... oops, the same paragraph, and pushes Publish Changes,
he can rest assured that .... the next week someone will say the bug in the article is still there!
He will think "I swore I fixed it."

We have no reason to know why the user did what he did.
But it is not fair to the user to make him think it worked!
Yes, "no success message means failure." Tough luck.

Yes, if an edit is saved, one will see the message 'Your edit was saved.' momentarily.
So, no message means no save.

OK. Please somebody notify all the affected Wikipedias.

Yes, using an incognito window, the page loads fine, in Mobile mode of course. This proves that reason why my browser is in a weird state is that I must have swallowed a cookie due to some tampering I did earlier. Doesn't matter. What does matter is to help users get out of that desktop mode if they ever end up in it.

Anyway most important is to give the user a big button at the top that says switch back to mobile view. Because he certainly doesn't remember why his browser is in this weird state. And he has little chance of finding the magic cure way down to the bottom of the page where it says says mobile view.

It might be very simple for the user to find the desktop view link on the mobile version, but much harder months later to figure out where such a link might be on the desktop version to switch back to mobile as it is much harder to find.

So maybe that cookie should expire in one day!

Okay it must be due to some cookie. I must have months ago pushed the desktop view button at the bottom of some Wikipedia page or something.

As you can see, we did not request the desktop site.

In https://bugs.chromium.org/p/chromium/issues/detail?id=1208366#c10
OGVs are seen as OGMs.

1. Download sample_640x360.ogv from https://filesamples.com/formats/ogv
2. Upload it on https://commons.wikimedia.org/wiki/Special:UploadWizard

Sure
we can
obviously write
on a
cell phone
it is
true,
but it is hard.

Also note it is rather hard to file a bug from a cellphone.

Real simple.
Say there is a file on your cellphone, that ends with the letters .ovg. And yes, it is a video file.

Browser: Firefox lite.

No, it's still is a video file thankfully. But you're using the filename extension for an audio file!

Now examining a Wikipedia page.

Google Chrome 92.0.4500.2 (Official Build) canary (32-bit)
Revision 4057a3002f0a89705f5ef98e35a232df46788dcf-refs/branch-heads/4500@{#4}
OS Android 8.0.0; ASUS_Z012DA Build/OPR1.170623.026

On YouTube, the user can see the second value filled in already, without needing to have to push the play button to trigger the computation.

Also when viewing the image, in the corner these have no mouseover saying what they do.
Maybe the middle one means make a comment on the image.

OK, I filed https://bugs.chromium.org/p/chromium/issues/detail?id=1205068 (which has my browser details.)

Here's the pencil!:
https://commons.wikimedia.org/w/index.php?title=File:Leaves_blown_backwards_.jpg&oldid=556775168
(It goes away once someone fills out the field.)

No cell phone needed. Just use
https://developer.chrome.com/docs/devtools/device-mode/

It is already in the code, just not in the blurb.

See also T281629.

And this stimulates the menu to grow...

OK, in the URL I used sort=last_edit_asc and what do you know, it worked.
Therefore the problem is just with the menu not mentioning it though it already works!

OK, in the URL we guess if desc means descending, what might ascending be... we guess wrong, but do trigger this message.

Anyways, To reproduce, simply go to a page that does not have any discussion at all yet and hit the red word Discussions; you'll see throughout the process we think we are creating a new discussion...