@Jonesey95: Nested flatlists do not display closing parentheses on mobile; see for example "People or cargo transported" in the infobox at Atlas V. I get the same issue with {{hlist}}, I'm guessing because they use the same class. @ネイ: I redirected the link in your comment to the archive.Hairy Dude (talk) 14:44, 20 February 2022 (UTC)[reply]
I don't know if second-level asterisks are formally supported in this template. I have added a case to the testcases, showing that there are missing closing parens after "Curiosity" and "Quasar" in mobile view. – Jonesey95 (talk) 18:25, 20 February 2022 (UTC)[reply]
One note: Removing "hlist-separated" from the class declaration removes the bullets and restores the closing parens. See the sandbox version in the mobile testcases link above. – Jonesey95 (talk) 23:16, 20 February 2022 (UTC)[reply]
Izno, based on the age of these phab tickets (see also the ill-fated T169315), it looks like we are on our own. Would it help to have a custom styles.css file for this template? – Jonesey95 (talk) 00:23, 21 February 2022 (UTC)[reply]
As I said, haven't done a lot of work with the hlist case. If that knocks out 4k, that works for me. Feel free to leave a link in the working section with the refined search. Izno (talk) 18:05, 22 February 2022 (UTC)[reply]
I've fixed this in mobile.css. We'll probably have to refix it when we get around to deploying the TemplateStyles version because when we do I want to review what hlist-separated is actually doing. Izno (talk) 22:43, 6 March 2022 (UTC)[reply]
I think it's because there is no |1= in the template page itself. When you say "seemingly stripped", what do you mean? To me, it appears to match the opening tag just fine, but it is needed only on this page (hence the noinclude tag). Is that closing tag causing an error somewhere? – Jonesey95 (talk) 00:18, 23 December 2020 (UTC)[reply]
I see </div> just before }} and then another one inside </div><noinclude>...</noinclude>, which, to my naive eye, seems to be stripped. I think you were trying to explain this to me above, so maybe you'll have to explain it at a more basic level, since I don't know why I should care about |1=. Anomalocaris (talk) 23:14, 28 December 2020 (UTC)[reply]
The template may be used in two differing ways: (i) like the first example at Template:Flatlist#Examples, where the entire list is passed into {{flatlist}} through its |1= parameter; (ii) like the example at Template:Flatlist#Alternative syntax, where the list is placed between {{startflatlist}} and {{endflatlist}}. In the case of (i), the single use of {{flatlist}} wraps the list in <div class="hlist hlist-separated">...</div>, which is a balanced tag pair; in the case of (ii), the {{startflatlist}} produces an unclosed <div class="hlist hlist-separated"> tag, and this is closed by the {{endflatlist}} which produces the balancing </div> tag (and nothing else). Now Template:Startflatlist is merely a redirect to Template:Flatlist, so the second example may be written
and this shows that when {{flatlist}} is used without parameters, some form of explicit closure is required, which is why there is that </div> after the <noinclude>. --Redrose64 🌹 (talk) 10:04, 29 December 2020 (UTC)[reply]
This edit request has been answered. Set the |answered= parameter to no to reactivate your request.
Please replace the live template with the sandbox version. This change does two things:
1. It moves the closing /div tag outside of the #if statement to match the opening div tag. This fixes an unclosed div tag error when the template is used with no input. See the relevant test case.
2. It adds standard template unknown parameter checking. There are currently 300+ pages using this template with unknown parameters, which is preventing desired information from being displayed. I just fixed an article that previously had an incorrect fix applied because this template was not displaying any error messages.
Not done: I am fairly certain your change would break the use of flatlist to start a flatlist, as in a pair of {{flatlist}} * A * B * C{{endflatlist}}, no? Izno (talk) 22:01, 3 June 2025 (UTC)[reply]
Ah, you are correct. I don't recall seeing that construction. I have modified the sandbox to implement only the parameter checking. – Jonesey95 (talk) 00:38, 4 June 2025 (UTC)[reply]
