Template:Infobox ispermanentlyprotected from editing as it is aheavily used or highly visible template. Substantial changes should first be proposed and discussed here on this page. If the proposal is uncontroversial or has been discussed and is supported byconsensus, editors may use {{edit template-protected}} to notify an administrator or template editor to make the requested edit. Usually, any contributor may edit the template'sdocumentation to add usage notes orcategories. Any contributor may edit the template'ssandbox. Functionality of the template can be checked usingtest cases.

This is thetalk page for discussing improvements to theInfobox template.

Put new text under old text.Click here to start a new topic. New to Wikipedia? Welcome!Learn to edit;get help. Assume good faith Be polite andavoid personal attacks Be welcoming to newcomers Seekdispute resolution if needed

Archives:1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20Auto-archiving period:3 months

	This template does not require a rating on Wikipedia'scontent assessment scale. It is of interest to the followingWikiProjects:
Infoboxes This template is within the scope ofWikiProject Infoboxes, a collaborative effort to improve the coverage ofInfoboxes on Wikipedia. If you would like to participate, please visit the project page, where you can jointhe discussion and see a list of open tasks.InfoboxesWikipedia:WikiProject InfoboxesTemplate:WikiProject InfoboxesInfoboxes

This diff from last year addeddisplay: table-row !important toModule:Infobox/styles.css. This caused issues with{{Infobox awards list}}, as the list of specific awards doesn't collapse; it should switch todisplay: none when the collapse button is toggled, but the !important property prevents this. Seethis discussion for more.

Can !important be safely removed from this style sheet? The diff includedthis file showingthis 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.RunningTiger123 (talk)03:49, 8 May 2025 (UTC)[reply]

I've removed it as it didn't look necessary to me either for the relevant skin.Izno (talk)15:44, 8 May 2025 (UTC)[reply]

Thanks! That seems to have done the trick.RunningTiger123 (talk)00:41, 9 May 2025 (UTC)[reply]

Perphab: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 changehttps://en.wikipedia.org/w/index.php?title=Module:Infobox/styles.css&oldid=1228964747 made byUser:Jdlrobson. Does anyone see a reason why that would not be the case ? —TheDJ (talk •contribs)09:10, 16 June 2025 (UTC)[reply]

There is a request atTemplate talk:Infobox sports season to implementexplanatory 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 atTemplate: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. — Martin(MSGJ · talk)21:42, 23 June 2025 (UTC)[reply]

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?Moxy🍁22:17, 23 June 2025 (UTC)[reply]

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 — Martin(MSGJ · talk)22:29, 23 June 2025 (UTC)[reply]

Its odd we have groups of article's so different than others and want to hide things all the time making things unaccessible. LikeTemplate:Toronto Raptors .... why are we hiding all the links in the header?Moxy🍁22:37, 23 June 2025 (UTC)[reply]

It's againstMOS:COLOUR which saysLinks should be clearly identifiable as links for readers. For some time now, I have been suggesting thatif navboxes need colours that are not the default, the approach taken by the religious people has its merits. See for examplethe 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. --Redrose64 🌹 (talk)08:18, 24 June 2025 (UTC)[reply]

Why are we talking about colour? It is not relevant to what is being discussed here — Martin(MSGJ · talk)10:07, 24 June 2025 (UTC)[reply]

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. --Redrose64 🌹 (talk)21:15, 24 June 2025 (UTC)[reply]

.... 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.Moxy🍁22:04, 24 June 2025 (UTC)[reply]

To the original question: examples please, of where these notes are present within the infobox. --Redrose64 🌹 (talk)08:18, 24 June 2025 (UTC)[reply]

There are some examples in the/testcases — Martin(MSGJ · talk)10:08, 24 June 2025 (UTC)[reply]

FWIW, I fixed theMOS:SMALLFONT accessibility problem at{{Infobox college basketball team}} that was caused by embedding a{{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 atLIU Sharks men's basketball. –Jonesey95 (talk)20:09, 26 June 2025 (UTC)[reply]

@Jonesey95: I added your solution to the accessibility problem toHelp:Footnotes#Issues. Inspired by a comment fromMSGJ, 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{{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.Taxman1913 (talk)19:02, 14 July 2025 (UTC)[reply]

These lines override some backgrounds in dark mode to#1f1f23. This is very close to the default infobox background of--background-color-interactive-subtle (#202122), but neither exactly the same nor different enough to distinguish these elements from the rest of the infobox. Is this intentional?EvenTwist41 (talk)01:21, 17 September 2025 (UTC)[reply]

I know if this isn't the perfect place to be discussing transclusion, but I've noticed a couple of timeline templates using the infobox template, that have the ability to collapse. Like these:

Template:Paramount Skydance evolution

Template:WildBrain evolution

I'm struggling to incorporate this on a MediaWiki wiki I'm creating. (Template:Paramount evolution - Altcyclopedia) Any idea how to do it? -BiggieSMLZ (talk)21:30, 4 October 2025 (UTC)[reply]

The classes in use in those templates arecollapsible and its friend. These classes are aliased locally tomw-collapsible and its friend, which is thestandard name. Try those names instead.Izno (talk)04:52, 5 October 2025 (UTC)[reply]

I insertedmw-collapsible in place ofcollapsed on my template ([https://altcyclopedia.miraheze.org/wiki/Template:Paramount_evolution?action=edit) , but it still had no effect.BiggieSMLZ (talk)09:59, 5 October 2025 (UTC)[reply]

It isrequested that an edit be made to thetemplate-protected template atTemplate:Infobox. (edit ·history ·last ·links ·sandbox ·edit sandbox ·sandbox history ·sandbox last edit ·sandbox diff ·test cases ·transclusion count ·protection log) This template must be followed by acomplete and specific description of the request, so that an editor unfamiliar with the subject matter could complete the requested edit immediately. Edit requests to template-protected pages should only be used for edits that are eitheruncontroversial or supported byconsensus. If the proposed edit might be controversial, discuss it on the protected page's talk pagebefore using this template. Consider making changes first to thetemplate's sandbox andtest them thoroughly here before submitting an edit request. To request that a page be protected or unprotected, make aprotection request. When the request has been completed or denied, please add the|answered=yes parameter to deactivate the template.

If you change line #167 inModule:Infobox from

if rowArgs.data then

to

if rowArgs.data and (args.decat ~= 'yes') then

then|decat=yes will also prevent categorizing because of ignored data cells.

I'd also suggest changing the module to useModule:Yesno since|decat=Yes doesn't work as intended, for example, as I discovered before adding the right parameter to the first example underTemplate:Infobox/doc#Examples in my local copy of the doc.Tactica (talk)19:50, 14 October 2025 (UTC)[reply]

(This discussion started atTemplate talk:Infobox social media personality#Layout when a user reported an infobox with two blank rows. I'm copying over my text from there.)

The blank rows are related to embedding using|child=yes. Almost all of thetestcases have a blank line or two, on both desktop and mobile, with this markup:

<tr><tdcolspan="2"class="infobox-full-data"><linkrel="mw-deduplicated-inline-style"href="mw-data:TemplateStyles:r1316064257"></td></tr>

One blank line is always created at the beginning of this wrapper template (in-between{{Infobox person}}'s rows and the custom rows for this infobox), and a second is created when embedding this template into another. Both are direct results of|child=yes, which creates a blank row where|title= would be listed. It simply does not suppress this row if the title is left blank. The blank row does NOT occur if you embed using|subbox=yes instead.This issue is actually already mentioned atTemplate:Infobox#Embedding. A workaround/solution is listed but it would have to be applied everywhere that|child=yes is used. This is something that should be fixed directly atModule:Infobox instead.

Can this possibly be fixed by someone familiar with how this module functions? I've searched through the talk page archives and it seems like thisissue may have been fixed in the past.Prefall21:09, 15 October 2025 (UTC)[reply]

The lack of suppression for this row is not shocking. It has to do with how infobox just magically sucks up child infoboxes into its structure. (That hack may somewhen go away, but not anytime soon.)

@Frietjes, if you're around, since you solved some of this the last go around.Izno (talk)23:53, 16 October 2025 (UTC)[reply]

Izno, it's been sometime since I looked at this code. my guess right now is that if we change the code block starting near line 52 to move the categories and templatestyles outside of the cells and to the top of the output this could fix the problem. I will try to find some time to look at it, but I need to brush up on my string processing commands first.Frietjes (talk)17:05, 20 October 2025 (UTC)[reply]

@Frietjes: I know you have a ton of other things you are working on, but I just want to voice that I wouldlove to see this fixed... It is causing an issue with basically anything that uses|module= viaModule:Template wrapper. For example all the Infoboxes inCategory:Templates calling Infobox sportsperson (23) orCategory:Templates calling Infobox person (24) have this issue. If I can be helpful in anyway, please ping me!Zackmann (^{Talk to me}/_{What I been doing})07:25, 22 October 2025 (UTC)[reply]

Zackmann08, feel free to work on it if you want. the "fixChildBoxes" function is supposed to make the output tidy by making sure the td, th, and tr tags are properly matched, but that might not be working either right now. the two ways I can see making this work are (a) have the generated empty rows styled with "display:none" or (b) detect when a child box is being passed without any content outside of the child box and insert that directly, without having it inside of a table cell. the second option seems nicer since it doesn't have extra blank rows marked as "display:none".Frietjes (talk)17:12, 22 October 2025 (UTC)[reply]

@Frietjes: so this may be beyond my talents, but I'll take a stab at it tonight.Zackmann (^{Talk to me}/_{What I been doing})17:20, 22 October 2025 (UTC)[reply]

Tried anything yet?Cosmo Skerry (talk)22:22, 23 October 2025 (UTC)[reply]

I will confess I have not... I've been stuck on other projects.Zackmann (^{Talk to me}/_{What I been doing})22:26, 23 October 2025 (UTC)[reply]

• Wikipedia template-protected edit requests

• Lua-based templates