Thanks for filing this task @XanonymusX !

I replicated the bug here

Ring Ring Lied is showing the collapsed infobox

I'm going to pull this onto the board for further investigation by our excellent developers.

@Dbrant , please feel free to move it if we should reconsider its priority.

Observation:
This doesn't seem to be happening on EN or FR

A question that does come to mind is how many articles are likely impacted by this workaround and the LOE to fix it for our users.

After checking in with @Dbrant and reviewing it on Mobile-HTML, it appears this is a bug for #product-infrastructure-team-backlog.

CC: @sdkim

Assuming this is about Mobile-Content-Service codebase in that case

Have updated it, now both Android and iOS app are affected!

We remove infoboxes that are also div elements. The reasoning behind that is unknown, (fun fact) I traced it back to the origin and this rule exists since the first prototype commit and was never documented.

We could investigate if it's fine to allow this rule to be removed for infoboxes, but for now, this is considered a Template edge case that should be fixed by the template editors. cc/ @ssastry

Well, there is a lot that has never been documented in MobileWeb as well … How should something like this be fixed by template editors? First of all, close to nobody uses the apps (especially among editors), so editors will not notice. Then, in the recommendations for mobile-friendly pages it says that such divs should use the infobox-container class. Would it still be removed in that case (as the class name contains infobox nonetheless)? Atm using that class doesn’t help though, as the current configuration of MoveLeadParagraph won’t recognise it anymore; and Mobile Web is more important than the apps. I recommend deleting that rule altogether.

@XanonymusX thanks for the information, these are very useful.

In T270981#6958051, @XanonymusX wrote:

Well, there is a lot that has never been documented in MobileWeb as well … How should something like this be fixed by template editors? First of all, close to nobody uses the apps (especially among editors), so editors will not notice.

I agree with you, we should put some effort to document the best practices for template editors regarding the outputs of the mobile apps (iOS and Android) and find a proper venue to ventilate this information among editors and guidance on how to preview it.

Then, in the recommendations for mobile-friendly pages, it says that such divs should use the infobox-container class. Would it still be removed in that case (as the class name contains infobox nonetheless)? Atm using that class doesn’t help though, as the current configuration of MoveLeadParagraph won’t recognize it anymore; and Mobile Web is more important than the apps. I recommend deleting that rule altogether.

I believe a further investigation in favor of removing the rule is worth it here since infoboxes have a more consistent behavior through different wikis.

I just want to align expectations regarding the possible fix. The project is currently under maintenance and template-specific behaviors will be considered low priority.

div.infobox elements are now activated since this patch has been merged. I've checked div.infobox usage in other wiki's environment. Noted that only DiscussionTool, wikistats and MobileFrontend extensions use it in some cases that should not be reflected in the mobileapps. More details from the similar issue here - https://phabricator.wikimedia.org/T262581#7281577.

Collapse table (div) from the Dutch wiki works fine. -https://de.wikipedia.org/api/rest_v1/page/mobile-html/Ring_Ring?theme=black, because div.infobox are now available along with table.ifobox