Page MenuHomePhabricator

Multiple-issues templates in page sections don't render in modal
Closed, ResolvedPublic3 Estimated Story Points


In the new page-issues treatment, multiple-issues templates that are placed in page sections don't show up in the page-issues modal.

This is visible on readers-web-master on page like Stone_Cold_Steve_Austin. Other pages with this template can be found on English wikipedia using this insource search.

Screen Shot 2018-09-03 at 13.24.12.png (1×2 px, 888 KB)
Screen Shot 2018-09-03 at 13.24.18.png (1×2 px, 283 KB)

This does not happen on pages that have a multiple-issues template in the lead section of the article, such as Organic_compound

Screen Shot 2018-09-03 at 13.31.08.png (1×2 px, 710 KB)
Screen Shot 2018-09-03 at 13.31.12.png (1×2 px, 403 KB)

Developer notes

For the sake of others trying to understand what the issue is here, I'll try to convey it to the best of my understanding. Unfortunately words are hard, so I made pictures to help.

On the page Samsung, there are two sections with multiple-issue templates, "Operations" and "Acquisitions and attempted acquisitions". The DOM structure between the two is virtually identical.

Screen Shot 2018-09-05 at 10.55.57.png (1×3 px, 1 MB)
Screen Shot 2018-09-05 at 10.56.45.png (1×3 px, 1 MB)
Acquisitions and attempted acquisitionsOperations

And yet, Acquisitions appears in the modal, but Operations doesn't!

The reason for this is that when we look foramboxes within sections, we split the sections into fake subsections when there is more than one heading, and when we look through that fake subsection, we only select the top-level ambox, whereas when we look through real sections, or sections that do not have subsections, we select all nested amboxes.

When we parse these amboxes further along, we run into a condition that checks if there is only one ambox in the selected set of nodes. If there is, then we proceed, but if there's "not exactly one" (i.e. more than one), then we stop, and the issued don't get added to the dataset that renders them in the modal.

To illustrate:

Acquisitions section

Works because the section doesn't have subsections, and all nested amboxes are selected.

Screen Shot 2018-09-05 at 12.24.03.png (1×3 px, 515 KB)

Operations section

Doesn't work because only the top level ambox is selected, which has nested amboxes inside.

Screen Shot 2018-09-05 at 12.25.34.png (1×3 px, 454 KB)

Event Timeline

Change 457688 had a related patch set uploaded (by Jdrewniak; owner: Jdrewniak):
[mediawiki/skins/MinervaNeue@master] Fix multiple-issues template in page sections

Change 457897 had a related patch set uploaded (by Jdrewniak; owner: Jdrewniak):
[mediawiki/extensions/MobileFrontend@master] Equalizing jQuery selectors in Page.findChildInSectionLead

ovasileva set the point value for this task to 3.Sep 4 2018, 4:16 PM

during estimation, we decided on a 3 for the time being and decided to also check in next Thursday to see if there is increased complexity revealed

Change 457688 abandoned by Jdrewniak:
Fix multiple-issues template in page sections

With a different approach to the following patch: /457897/

This change is not necessary.

Change 457897 merged by Jdlrobson:
[mediawiki/extensions/MobileFrontend@master] Change Page.findChildInSectionLead to return nested elements

@Jdlrobson, @Tbayer - unsure of how this made its way into signoff...

The bug is fixed. QA will happen as part of T191532.

Jdlrobson added a subscriber: Niedzielski.

I ran through this with @Tbayer @Jdrewniak and @Niedzielski and this appears to be implemented as expected
I've added some exploratory QA steps to T191532 to cover this scenario further.