The Wikipedia app on iOS often crops lead images to the top third, showing only people's hair line.
I thought this bug was fixed ten years years ago, but I noticed the bug again in a recent unrelated WMF slidedeck, which prompted me to install the app and have a fresh look. I couldn't find an open task about it, hence filing a new one.
As I'm looking at it today, the issue appears worse than I remember. I forgot that we don't just add a banner on top, but also **remove** the photo from the default view of the article. So a person opening an article and reading the first few paragraphs and scrolling down, will never see the photo. (After I went looking for it, it wasn't obvious to me that the banner is clickable, and once I tried that, it seemed unreliable and required multiple taps to respond. Perhaps the click target clashes with something else. Or is the visual transition is blocked behind a web request?)
### Cultural significance
This bug does not merely move focus or shift attention to the top, it omits the majority of the photo and thus completely misses the sentiment that a photo is meant to convey to the reader. Consider the Queen of Shiba and Prince Eugene paintings and how much cultural context is lost.
The **Mona Lisa does not appear on the Mona Lisa article** in the iOS app. The face of the subject does, but the painting is not there.
The Night Watch by Rembrandt is missing the young girl with the chicken and militiaman figure in white, that make the painting famous for its use of light and shadow.
I know these are technical issues, but from an end-user perspective this is editorial control and interference. The app is redefining what art looks like, redefining what people are known for and how they express themselves, and overriding editors curating and carefully choosing photos to convey information and context to readers. These aren't just tiny thumbnails in an array of search results shown in the middle of a workflow, or secondary photos further down the article. This is **the** lead photo, on top of **the** one article the reader has chosen to open and learn more about. And in the moment where we are expected to present them the best we have, we present this:
### Current result
{F70821102 width=150, layout=inline} {F70821167 width=150, layout=inline} {F70821218 width=150, layout=inline} {F70821313 width=150, layout=inline} {F70821406 width=150, layout=inline} {F70821429 width=150, layout=inline} {F70821508 width=150, layout=inline} {F70821498 width=150, layout=inline} {F70821075 width=150, layout=inline} {F70821293 width=150, layout=inline} {F70821304 width=150, layout=inline}
The examples are from using the app for five minutes after a fresh install on an iPhone, searching for common first names/titles (Alice, Charles, Irene, Patricia, Queen, Prince, etc) and selecting a high-ranking article from the search suggestions:
* https://en.wikipedia.org/wiki/Irene_van_Dyk
* https://en.wikipedia.org/wiki/Alice_Cooper
* https://nl.wikipedia.org/wiki/PATRICIA
* https://en.wikipedia.org/wiki/Charles_de_Montesquieu
* https://en.wikipedia.org/wiki/Queen_of_Sheba
* https://en.wikipedia.org/wiki/Prince_Eugene_of_Savoy
* https://en.wikipedia.org/wiki/The_Night_Watch
* https://en.wikipedia.org/wiki/Mona_Lisa
* https://en.wikipedia.org/wiki/Bento_Costa_Lima
* https://en.wikipedia.org/wiki/Richard_Branson
* https://en.wikipedia.org/wiki/Tom_Brady
### Real photos
As shown on desktop web, mobile web, and Android.
{F70821103 width=150, layout =inline} {F70821169 width=150, layout=inline} {F70821222 width=150, layout=inline} {F70821339 width=150, layout=inline} {F70821413 width=150, layout=inline} {F70821426 width=150, layout=inline} {F70821723 width=150, layout=inline} {F70821503 width=150, layout=inline} {F70821077 width=150, layout=inline}
### Other information
[Recent WMF slidedeck](https://docs.google.com/presentation/d/1nWurSh82kw9EeSn1v4TrEFRpoe8udQbWZu7agwHPMf0/edit):
{F70821040 height=200}
Related tasks:
* {T93829}
* {T104480}
* {T131424}
* {T148926}
* {T156217}
* {T214718}
* {T229534}