Page MenuHomePhabricator

Unescaped HTML in page titles on file pages in the Android app
Closed, ResolvedPublicBUG REPORT


Steps to replicate the issue (include links if applicable):

What happens?:

  • The title of the file page has unescaped HTML

Screenshot_20221203-151636.png (2×1 px, 958 KB)

To me it looks like the app takes the title (which now usually contains some span tags as of a few months ago), and removes everything up to the first colon, which explains why the tags are unbalanced.

What should have happened instead?:
The title should not have unescaped HTML.

Software version (skip for WMF-hosted wikis like Wikipedia)
App version: 2.7.50422-r-2022-10-24

Other information (browser name/version, screenshots, etc.):

Event Timeline

Click "Read article" (why is it called that when you click an image, btw?)

This sounds strange -- where do you see "Read article" when looking at the image? (can you post a screenshot of that?)

Screenshot_20221203-163352.png (2×1 px, 1 MB)

Just pressed the picture itself, and this comes up:

Screenshot_20221203-163402.png (2×1 px, 933 KB)

The loading circle thing just keeps loading forever as well.

hmm, that's definitely not the expected behavior, and not reproducible for me. (tapping the image should just take you to a full-screen view of the image.)

Screenshot_20221203_104925.png (2×1 px, 3 MB)

May I ask what device model, and what version of Android you're using? And have you made any unusual changes in the settings of the app?
Also, is this happening for images in all articles, or just this one?

I haven't made any changes to it, and it's the standard version (version number is in the task). The device is a Nokia X20, Android 12.

I've checked other articles, and in those everything works as expected. The only slightly unusual thing about this specific image in the wikitext is that it has an |alt= text, but it would be weird for that to affect anything.

My only guess so far would be some kind of weird cached version of that article stuck in the app's browser cache. Would you be able to try clearing the app's cache, and trying again? (go to "App Info" -> Storage -> Clear cache)

Dbrant claimed this task.