On wikidata.org currently, this is how mobile editing of statements shows some of the ranks while editing.
While viewing this appears fine.
I believe this was on the mobile view of https://www.wikidata.org/wiki/Q4115189
| Addshore | |
| Mar 13 2026, 4:52 PM |
| F80263507: Screenshot_20260508-092348.png | |
| May 8 2026, 8:24 AM |
| F80263508: Screenshot_20260508-092344.png | |
| May 8 2026, 8:24 AM |
| F73156453: image.png | |
| Mar 19 2026, 3:48 PM |
| F73014511: screen-20260316-092007-1773652787069.mp4 | |
| Mar 18 2026, 7:50 AM |
| F72834816: image.png | |
| Mar 13 2026, 4:52 PM |
On wikidata.org currently, this is how mobile editing of statements shows some of the ranks while editing.
While viewing this appears fine.
I believe this was on the mobile view of https://www.wikidata.org/wiki/Q4115189
So, I reproduced this right away (with phone screen recording) yesterday.
I click the link to the item in this ticket, I scroll down to the edit links for statements, click edit and the issue can be seen.
Apparently the recording is too big for phab, and my commons upload attempt failed (will try again later)
Pixel 9 pro, chrome
Following the steps to reproduce, I do not encounter this on mocked android or an iphone se 2 gen:
@Addshore , can you also provide context of how your wikidata preferences are set up? e.g. what beta features are enabled, if you have any specific skins in use, etc?
Tested this morning in incognito on the same phone on a fresh user account where the only setting change is to turn on the beta feature, and I still have the issue.
Is there any advanced setup extension wise? I can have a go reproducing locally if someone gives me a pointer or two.
There shouldn’t be a lot of special setup needed – install Wikibase (master, not any release branch), make sure composer dependencies are installed, enable $wgWBRepoSettings['tmpMobileEditingUI'] = true; (and $wgWBRepoSettings['tmpEnableMobileEditingUIBetaFeature'] = true; if you want it as a beta feature instead of unconditionally enabled), install MobileFrontend and load pages with ?useformat=mobile. (Some data types would need additional extensions and/or configuration but it doesn’t sound like that should be relevant here.)