View source for Template talk:Infobox

{{Permanently protected}}
{{talkheader}}
{{WikiProject banner shell|
{{WikiProject Infoboxes}}
}}
{{User:MiszaBot/config
|archiveheader = {{talkarchivenav}}
|maxarchivesize = 75K
|counter = 19
|minthreadsleft = 6
|algo = old(90d)
|archive = Template talk:Infobox/Archive %(counter)d
}}
{{Lua sidebar}}

== Parameters with space in the name ==

There might be some valid reasons why two-word parameter names to be spelled with an underscore in the middle, but I would like to propose an easy-to-implement idea of adding a simple input preprocessor to accommodate the users who cannot memorize which template expects an underscore and which expects a space.

As this preprocessor is meant to be added in front (without '|list'), without requiring any change in the tried-and-tested template itself, implementation should be simpler than making many changes in different locations:
<syntaxhighlight lang=lua>
{{#invoke:params|renaming_by_replacing|%s|_|1|list}}
</syntaxhighlight>

On Chrome browser, the character following '%s|' in the above line appears indistinguishable from a space, but it is an underscore. This symptom might further highlight the benefit of adding this preprocessor. If a space is found in the middle of parameter names, this line replaces it with an underscore (only once on each parameter name, for as many parameters there may be).  It leaves single-word parameter names and those parameter names spelled with underscore as is, and it is meant only for those templates that expect an underscore. As a result of adding the line, the template will accept a space where an underscore is expected to join two words in parameter names.

What I don't know is where and how best to place it, if it is possible and desirable to place it on Template:Infobox to take care of its child templates at once, or on each child like [[Template:Infobox Treaty]].  And further I don't know if any child template uses parameter names with a space.  I would help in editing the doc pages for the change if needed.<br>
[[User:Yiba|<span style="color:#B20000;">Yiba</span>]] ([[User talk:Yiba|talk]] | [[Special:Contributions/Yiba|contribs]]) 16:29, 12 February 2025 (UTC)
:Feel free to implement this in a sandbox template or module and show how it works. You'll need to account for all sorts of bad choices by template editors. For example: What happens in the degenerate case where there are two distinct parameters, one with a space and one with an underscore but otherwise identical? – [[User:Jonesey95|Jonesey95]] ([[User talk:Jonesey95|talk]]) 19:04, 12 February 2025 (UTC)
::Thanks.  May be a bit difficult to read, but a demo is at: [[User:Yiba/sandbox/infobox]]
::In this demo, parameters "former_name=Former Name" and "former name=degenerate case" are specified.  The first parameter with an underscore is unchanged, and the second parameter is changed by the above line to "former_name=degenerate case" ending up two parameters with the same name.  When this occurs, the 'changed' parameter name takes precedence, as it is the spec for "params|renaming by replacing", so the original "former_name=Former Name" is discarded with no harm done.<br><br>
::In an even more foolish case where "|former_name=Former Name|" and "|former name=|" are specified, "former name" is converted into "former_name" and passed without data, with no harm.<br><br>
::In the most degenarate case where "|former name|" is in the line, '1' is prepended as the param name and "1=former name" (without being converted, as neither 'former' nor 'name' is considered as a param name) is passed.  As '1' is unknown to Template:Infobox Treaty as a parameter name, it is ignored without harm.<br><br>
::I cannot figure out how to incorporate the line into the template, but as I am not a template editor, I'd need your further help regardless.  [[User:Yiba|<span style="color:#B20000;">Yiba</span>]] ([[User talk:Yiba|talk]] | [[Special:Contributions/Yiba|contribs]]) 04:11, 13 February 2025 (UTC)
:An easy solution is to just change the templates that use spaces. [[User:Gonnym|Gonnym]] ([[User talk:Gonnym|talk]]) 11:42, 13 February 2025 (UTC)
::Do you know the reason why this template uses underscore, and not the space? I feel there are much more templates, especially those frequently used for editing, that use space rather than underscore. [[User:Yiba|<span style="color:#B20000;">Yiba</span>]] ([[User talk:Yiba|talk]] | [[Special:Contributions/Yiba|contribs]]) 01:11, 18 February 2025 (UTC)
:::[[MOS:INFOBOXNAME]]: {{tq|Use snake case (e.g. {{para|birth_date}}). Not camel case (e.g. {{para|birthDate}}) or title case (e.g. {{para|BirthDate}})}}  and {{tq|represent spaces using an underscore, e.g. {{para|birth_place}} not {{para|birth-place}} or {{para|birth place}}}} .[[User:Gonnym|Gonnym]] ([[User talk:Gonnym|talk]]) 09:42, 18 February 2025 (UTC)
::::There are a few parameter  names in {{t|infobox}} itself that should be converted to snake, fwiw. [[User:Primefac|Primefac]] ([[User talk:Primefac|talk]]) 14:58, 18 February 2025 (UTC)
::::Thank you.  Now I understand changing Infobox spec may be a daunting task.<br>
::::However:
::::1. "Better for the users" should take priority over "easier to code".
::::2. Manuals are written about something pre-existing. Infobox was coded before the manual was written, and its features were not determined because the manual said so.
::::3. As I have stated, I am willing to rewrite docs, including the MOS if necessary.
::::4. My proposal does not subtract any functionality. 
::::5. The proposal does accommodate users better.
::::What do you think?  [[User:Yiba|<span style="color:#B20000;">Yiba</span>]] ([[User talk:Yiba|talk]] | [[Special:Contributions/Yiba|contribs]]) 02:46, 20 February 2025 (UTC)
:::::I disagree that spaces are better. [[User:Gonnym|Gonnym]] ([[User talk:Gonnym|talk]]) 09:48, 20 February 2025 (UTC)
::::::I am not saying space is better.  I am saying accepting underscore AND space is more user-friendly. This proposal does not reduce convenience for the users who prefers underscore. [[User:Yiba|<span style="color:#B20000;">Yiba</span>]] ([[User talk:Yiba|talk]] | [[Special:Contributions/Yiba|contribs]]) 00:25, 21 February 2025 (UTC)
:::::::I'll be blunt and say I don't care what a specific user prefers or does not prefer. We should have one consistent style (whichever it may be) and use that. That isn't something unique to Wikipedia. Every good language has a naming convention. This allows everyone using the system to know what to expect. [[User:Gonnym|Gonnym]] ([[User talk:Gonnym|talk]]) 10:44, 21 February 2025 (UTC)
::::::::I understand Wikipedia is many different things for different people.  But I am sure it was and is NOT meant for the use by programmers (unlike programming tools).  The English language uses space (or, sometimes hyphen) in between words, so if we have to standardize and choose between a space and underscore, the choice is clear that it should be the space.
::::::::I am not arguing for standardization, but for the vast majority of English-speaking users and editors of en.wikipedia, a natural expectation would be the system to accept a space connecting two-word names.  I don't mind the system expecting an underscore, but allowing the use of space (in addition to underscore) is more user-friendly. [[User:Yiba|<span style="color:#B20000;">Yiba</span>]] ([[User talk:Yiba|talk]] | [[Special:Contributions/Yiba|contribs]]) 05:51, 25 February 2025 (UTC)
{{edit template-protected|Module:Infobox/styles.css|demo=yes|answered=yes}}
:::::::::I have solicited opinions on the above discussion at [[Wikipedia talk:WikiProject Infoboxes]], and am adding edit request to it now.  Please help me implement this change, as I cannot edit the Infobox template, or its components myself.<br>
:::::::::[[User:Yiba|<span style="color:#B20000;">Yiba</span>]] ([[User talk:Yiba|talk]] | [[Special:Contributions/Yiba|contribs]]) 05:15, 9 March 2025 (UTC)
::::::::::There is no consensus for this change. The edit request template is for uncontroversial change requests. – [[User:Jonesey95|Jonesey95]] ([[User talk:Jonesey95|talk]]) 02:40, 10 March 2025 (UTC)
:To add another user to the mix, we should not support this. It will make maintenance more difficult for the pretty arbitrary desire to have one or the other kinds of parameters. If you specifically have issues with templates, consider using the templatewizard (in 2010 editor) or the template insertion dialog (in VisualEditor) to do the work for you. (And if those don't work, that's a TemplateData issue that needs to be resolved, which I suspect you are smart enough to fix for arbitrary template.) [[User:Izno|Izno]] ([[User talk:Izno|talk]]) 02:21, 12 March 2025 (UTC)
:: {{tq|It will make maintenance more difficult}}: This is just a technical comment (I have no opinions on the “space vs underscore” debate). There are many ways to implement this with {{mfl|params}}. The easiest way is that the current {{tl|Infobox}} template gets moved verbatim to a subtemplate (e.g. {{tl|Infobox/underscores}}) and the content of the new {{tl|Infobox}} becomes the following:
:: <syntaxhighlight lang="wikitext">{{#invoke:params|renaming_by_replacing|%s+|_|concat_and_call|Infobox/underscores}}</syntaxhighlight>
:: By doing so, the old {{tl|Infobox/underscores}} will keep dealing with underscores as it always did (no spaces there), whereas the user will be able to use both spaces and underscores. This also adds a third possibility to this debate: leaving {{tl|Infobox}} as it is, and creating a wrapper template called {{tl|Spaced infobox}} (or whatever) containing the code above (with <code>Infobox</code> instead of <code>Infobox/underscores</code>). --[[User:Grufo|Grufo]] ([[User talk:Grufo|talk]]) 15:33, 21 April 2025 (UTC)

== Display on narrow screens ==

If you look at pages like [[Jimmy Greaves]] on a device with a narrow screen, either a mobile in desktop view or a regular computer with a small window, the infobox displays above the text with the normal width for the content, but the border is at full screen width. To see the problem, reduce the window size until it reaches a critical width (possible 640px) and the infobox jumps above the text and changes appearance. Looking at the examples in the documentation for {{tl|infobox football biography}} you see the same for Alev Kelter, where the border is full screen and the infobox content is to the left of the box bounded by the border (see [[Template:Infobox_football_biography#Embedding_other_infoboxes_(module_parameter)|here]]). However, another example for Tim Template switches to using the full width for the infobox, so the infobox is now wider than in larger window (see [[Template:Infobox_football_biography#Independent|here]]).

Both those infoboxes use {{tl|infobox football biography}} Other infobox such as {{tl|infobox settlement}} don't show this behaviour (e.g. see  [[Manchester]]), but the behaviour seems to originate with {{tl|infobox}} as you can see it in the documentation for this template (see [[Template:Infobox/doc|here]].

I can't work out why this happens, why {{tl|infobox settlement}} doesn't show the same, or why the Tim Template example has a different behaviour. &nbsp;—&nbsp;<span style="white-space: nowrap;font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> [[User:Jts1882|Jts1882]]  &#124;[[User talk:Jts1882| talk]]&nbsp;</span> 10:36, 21 April 2025 (UTC)

:Yes, the breakpoint width is currently defined as 640px.
:Infobox football bio has had a max-width of 420px set, which is why it does not go to full width as might be expected. This can be fixed by giving it a TemplateStyles sheet and then making the width a media query (as is done with infobox settlement below).
:Infobox settlement likewise loads a width of 23em at all widths rather than the relevant breakpoint. I've [https://en.wikipedia.org/w/index.php?title=Template%3AInfobox_settlement%2Fstyles.css&diff=1286716700&oldid=1043192559 now adjusted] that to go full width below the breakpoint, or whatever other behavior is plugged into the relevant CSS (on Minerva it's full width, on Vector 22 it's something a bit different but only incidentally as infoboxes are currently tables). [[User:Izno|Izno]] ([[User talk:Izno|talk]]) 15:34, 21 April 2025 (UTC)
:: Your change to Infobox settlement only changes the outer border of the infobox. The content (rows and cells) only fill part of the width. I don't understand why they don't fill the full table width. As far as I can tell the row width is controlled by the size of the images. Increasing the image size also increases the width above the 640px when bigger than the 23em. &nbsp;—&nbsp;<span style="white-space: nowrap;font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> [[User:Jts1882|Jts1882]]  &#124;[[User talk:Jts1882| talk]]&nbsp;</span> 08:46, 22 April 2025 (UTC)
:::Yes, that's what {{tq|on Minerva it's full width, on Vector 22 it's something a bit different but only incidentally as infoboxes are currently tables}} implies. Below the break point Minerva has a ton of CSS to make this look "pretty", that needs assessment at some point (and which I'd prefer to defer until after infobox is not a table but instead a collection of divs). Vector22 on the other hand, because an infobox is a table, has some CSS which causes this "bad" look but which is valuable for tables more generally. [[User:Izno|Izno]] ([[User talk:Izno|talk]]) 15:16, 22 April 2025 (UTC)
:::: OK, with you now. You don't really need the <code>@media min-width</code> block as all it is doing is setting the width to 23em, rather than using the default infobox class width of 22em.
:::: It's a bit odd that the <code>tbody</code> and <code>tr</code> elements aren't using the full width of the <code>table</code>, but there is a fix for the others skins using a <code>@media max-width</code> block:
:::: <syntaxhighlight lang=css>
@media (max-width: 640px) {
	body:not(.skin-minerva) .ib-settlement th.infobox-header  {
		width:50%;
	}
}</syntaxhighlight>
:::: The 50% width works because headers span two columns in {{tl|infobox settlement}}. Other infoboxes would need different values. &nbsp;—&nbsp;<span style="white-space: nowrap;font-family:Arial;background:#d6ffe6;border:solid 1px;border-radius:5px;box-shadow:darkcyan 0px 1px 1px;"> [[User:Jts1882|Jts1882]]  &#124;[[User talk:Jts1882| talk]]&nbsp;</span> 11:48, 28 April 2025 (UTC)
:::::Which I've been trying to avoid introducing because it will just be a pile of hacks to undo (including for when at some point we do get to the land of divs since the ideal is that infoboxes scale down to one line for a label and one line for data) and which might be emulated in downstream or other infoboxes. There are indeed clear and obvious-ish solutions here and there, but they're all for a resolution which displays reasonably if not perfectly for a skin (or three) that I don't think we need to optimize for in the meantime. [[User:Izno|Izno]] ([[User talk:Izno|talk]]) 17:06, 28 April 2025 (UTC)

== Display for table rows ==

{{diff2|1228942011|This diff}} from last year added <code>display: table-row !important</code> to [[:Module:Infobox/styles.css]]. This caused issues with {{tl|Infobox awards list}}, as the list of specific awards doesn't collapse; it should switch to <code>display: none</code> when the collapse button is toggled, but the !important property prevents this. See [[Template talk:Infobox awards list#Collapsible feature not working|this discussion]] for more.

Can !important be safely removed from this style sheet? The diff included [https://phabricator.wikimedia.org/F55300125 this file] showing [[Chris Dangerfield|this page]], and when I go there and edit the CSS in my browser, removing that property doesn't seem to cause issues. However, I am not nearly enough of a CSS expert to know if other issues could arise somewhere. [[User:RunningTiger123|RunningTiger123]] ([[User talk:RunningTiger123|talk]]) 03:49, 8 May 2025 (UTC)

:I've removed it as it didn't look necessary to me either for the relevant skin. [[User:Izno|Izno]] ([[User talk:Izno|talk]]) 15:44, 8 May 2025 (UTC)
::Thanks! That seems to have done the trick. [[User:RunningTiger123|RunningTiger123]] ([[User talk:RunningTiger123|talk]]) 00:41, 9 May 2025 (UTC)

== Automatic dark mode fix ==

Per [[phab:T396988]] I think that line 45 should end with [style], analogous to its night mode variant just above. It seems to me that this was missed in change https://en.wikipedia.org/w/index.php?title=Module:Infobox/styles.css&oldid=1228964747 made by [[User:Jdlrobson]]. Does anyone see a reason why that would not be the case ? —[[User:TheDJ|Th<span style="color: green">e</span>DJ]] ([[User talk:TheDJ|talk]] • [[Special:Contributions/TheDJ|contribs]]) 09:10, 16 June 2025 (UTC)

== Notelist inside infobox ==

There is a request at [[Template talk:Infobox sports season]] to implement [[Help:explanatory notes|explanatory notes]] inside the infobox, to avoid the notes getting confused with other groups of notes lower down the article. Apparently this has already been done at [[Template:Infobox college basketball team]]. I'm posting here in case anyone has an opinion about this, or whether this could more efficiently be coded at the meta module instead. &mdash;&nbsp;Martin <small>([[User:MSGJ|MSGJ]]&nbsp;·&nbsp;[[User talk:MSGJ|talk]])</small> 21:42, 23 June 2025 (UTC)

:So just to be clear there are infoboxs out there that have the footnotes at the end of the info box making the box longer with notes that are in very small text? Why would we clutter the lead in this way? I think I have seen this before..... this is something that pop culture articles do? <span style="display:inline-flex;rotate:-15deg;color:darkblue">'''[[User:Moxy|Moxy]]'''</span><span style="display:inline-flex;rotate:15deg;color:darkblue">[[User talk:Moxy|🍁]]</span> 22:17, 23 June 2025 (UTC)
::I have not noticed these infoboxes previously. I think small text is a bad idea because infoboxes are already at a smaller size. The proposal at Infobox sports season is a collapsed box with the notes in &mdash;&nbsp;Martin <small>([[User:MSGJ|MSGJ]]&nbsp;·&nbsp;[[User talk:MSGJ|talk]])</small> 22:29, 23 June 2025 (UTC)
:::Its odd we have groups of article's so different than others and want to hide things all the time making things unaccessible. Like [[Template:Toronto Raptors]] .... why are we hiding all the links in the header? <span style="display:inline-flex;rotate:-15deg;color:darkblue">'''[[User:Moxy|Moxy]]'''</span><span style="display:inline-flex;rotate:15deg;color:darkblue">[[User talk:Moxy|🍁]]</span> 22:37, 23 June 2025 (UTC)
::::It's against [[MOS:COLOUR]] which says {{tq|Links should be clearly identifiable as links for readers.}} For some time now, I have been suggesting that ''if'' navboxes need colours that are not the default, the approach taken by the religious people has its merits. See for example [[Tricia Hillas#References|the navboxes at Tricia Hillas]]. Only the topmost bar is styled, to have: background white; unlinked text black; linked text default; top and bottom borders coloured. --[[User:Redrose64|<span style="color:#a80000; background:#ffeeee; text-decoration:inherit">Red</span>rose64]] &#x1f339; ([[User talk:Redrose64|talk]]) 08:18, 24 June 2025 (UTC)
:::::Why are we talking about colour? It is not relevant to what is being discussed here &mdash;&nbsp;Martin <small>([[User:MSGJ|MSGJ]]&nbsp;·&nbsp;[[User talk:MSGJ|talk]])</small> 10:07, 24 June 2025 (UTC)
::::::Moxy asked "why are we hiding all the links in the header?" To me they're hidden by being the same colour as the unlined text. --[[User:Redrose64|<span style="color:#a80000; background:#ffeeee; text-decoration:inherit">Red</span>rose64]] &#x1f339; ([[User talk:Redrose64|talk]]) 21:15, 24 June 2025 (UTC)
:::::::.... Perhaps I better be more clear here. Why is it that sports projects go out of their way to hide links and information in most of their templates..... for example colored links and of hiding the sources/notes in an info box. <span style="display:inline-flex;rotate:-15deg;color:darkblue">'''[[User:Moxy|Moxy]]'''</span><span style="display:inline-flex;rotate:15deg;color:darkblue">[[User talk:Moxy|🍁]]</span> 22:04, 24 June 2025 (UTC)
:::To the original question: examples please, of where these notes are present within the infobox. --[[User:Redrose64|<span style="color:#a80000; background:#ffeeee; text-decoration:inherit">Red</span>rose64]] &#x1f339; ([[User talk:Redrose64|talk]]) 08:18, 24 June 2025 (UTC)
::::There are some examples in the [[Template:Infobox sports season/testcases|/testcases]] &mdash;&nbsp;Martin <small>([[User:MSGJ|MSGJ]]&nbsp;·&nbsp;[[User talk:MSGJ|talk]])</small> 10:08, 24 June 2025 (UTC)
FWIW, I fixed the [[MOS:SMALLFONT]] accessibility problem at {{tl|Infobox college basketball team}} that was caused by embedding a {{tl|notelist}} inside an infobox. That sort of fix would be needed for any other infobox that included the same embedding. You can see notes in an infobox at [[LIU Sharks men's basketball]]. – [[User:Jonesey95|Jonesey95]] ([[User talk:Jonesey95|talk]]) 20:09, 26 June 2025 (UTC)

:{{re|Jonesey95}} I added your solution to the accessibility problem to [[Help:Footnotes#Issues]]. Inspired by a comment from [[User:MSGJ|MSGJ]], I looked at several infoboxes that allow for the display of footnotes. They generally do so by creating a series of parameters, which limits the number of footnotes available (not necessarily a bad thing). I did not find any others that call {{tlx|notelist}}, which seems far more simple to me. Hopefully, if anyone else decides to implement this, they will see the note I left on the help page. I'm glad MSGJ reached out this talk page for advice. Thanks for your help. [[User:Taxman1913|Taxman1913]] ([[User talk:Taxman1913|talk]]) 19:02, 14 July 2025 (UTC)

== Overridden dark mode background is almost but not identical to default ==

[https://en.wikipedia.org/w/index.php?title=Module:Infobox/styles.css&oldid=1295905060#L-33--L-50 These lines] override some backgrounds in dark mode to <code>#1f1f23</code>. This is very close to the default infobox background of <code>--background-color-interactive-subtle</code> (<code>#202122</code>), but neither exactly the same nor different enough to distinguish these elements from the rest of the infobox. Is this intentional? [[User:EvenTwist41|EvenTwist41]] ([[User talk:EvenTwist41|talk]]) 01:21, 17 September 2025 (UTC)