in the absense of manual sorting that we used to have, it would at least be super nice if preferred statements within a statement group were displayed at the top. likewise, deprecated statements should be displayed at the bottom of the group.
I can't see this being so complicated or difficult to do.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Jdlrobson | T78430 [Epic] Getting Wikidata to render nicely on mobile web | |||
| Open | None | T158181 Aim for workflow equivalence for MediaWiki on desktop and mobile web | |||
| Open | None | T95878 [Story] Make Wikidata editable on mobile web | |||
| Open | None | T95649 Create and document a stable framework for extending the Wikibase UI | |||
| Stalled | None | T40968 Keyboard-navigability of the repo UI | |||
| Open | None | T54136 [Epic] Redesign Item UI for Wikidata repo | |||
| Open | None | T87316 [Story] Redesign statement section | |||
| Duplicate | None | T115054 [Story] Sort statements (within property group) at least by rank, with preferred at the top and deprecated at the bottom |
example, I just added the new(ish) mayor of Washington D.C. to Q61, marked her as preferred and changed rank of the old mayor back to normal
https://www.wikidata.org/wiki/Q61
it's annoying to have the new mayor at the bottom and that perhaps the only way currently to fix (afaik) is to remove and readd (or via api editentity)
How does this differ from T87327: [Story] Group statements within statement group by ranks?