Page MenuHomePhabricator

Content for specific article not appearing in mobile-html
Closed, ResolvedPublic

Description

The article [[Pomelo]] on enwiki is missing all of its content except the infobox, when viewed through mobile-html:

https://en.wikipedia.org/api/rest_v1/page/mobile-html/Pomelo


original submission:

from OTRS:
https://ticket.wikimedia.org/otrs/index.pl?Action=AgentTicketZoom;TicketID=11563822#

Hi, when viewed in the Android app, the main information section of article https://en.wikipedia.org/wiki/Pomelo?wprov=sfla1 is missing compared to when viewed in browser:

app.jpg (6×1 px, 859 KB)

browser.jpg (11×1 px, 1 MB)

I've checked the app is up to date, and checked the article on a couple of different phones with the same result, so I assume it's an app/article issue rather than a hardware issue.

Note this is happening on both Android and iOS apps.

Event Timeline

Dbrant renamed this task from Main content of article appears on web but not in app to Content for specific article not appearing in mobile-html.Oct 23 2020, 4:04 PM
Dbrant triaged this task as High priority.
Dbrant updated the task description. (Show Details)

For what it's worth, Parsoid is designating all sections of this article other than the lead section as non-editable (data-mw-section-id="-1"). They may want to investigate that. It seems to be the case going several revisions back, which suggests that the real culprit is probably a recent change to a transcluded template. Still, it's a bug for that to break mobile-html in this way, so a mobileapps update will be needed in any case.

Looks like this article was using {{stack begin}} without a corresponding {{stack end}}. Fixed in this diff which appears to have fixed it in the apps.

ssastry subscribed.

Thanks @Pcoombe! Nothing for use to do here. I am going to untag Parsoid here.

Yes, thanks very much for fixing that, @Pcoombe!

I am still trying to understand where exactly mobile-html went off the rails, but perhaps it's not worth sinking that much time into it. It does look like Domino (JS), while building up the DOM, gets tripped up by the large data-mw attribute of the style element near the top of the page.

Mholloway assigned this task to Pcoombe.

Most of the article content got zapped during the swapping in of the collapsible infobox. It was contained within the replaced div because of the erroneous template usage. I'm satisfied calling this one a content issue and not a mobileapps bug.