Template talk:Military navigation

Always shown

Due to a bug fix with Common.js, these will now always be shown, no matter how many appear on a page. If you wish to fork this template to a version always hidden, add to the NavContent style="display:none;...." ←Ben^B4 13:29, 8 August 2007 (UTC)

Interesting; this will allow us to have a "noshow" style on this template. Thanks for the suggestion! Kirill 01:38, 9 August 2007 (UTC)

Please do not do that. It won't work for users who have Javascript disabled. Rather use class="NavFrame collapsed" in the outer div. —AlanBarrett (talk) 21:30, 4 February 2009 (UTC)

Convert to navbox from navbox generic

I'm requesting that the "navbox generic" template call be replaced by the "navbox" template. The navbox is the new standard style. There should be no significant visible changes to instances of this template, only changes in how the underlying code is structured (and standardization). All that needs to be done is to delete the word "generic" in the first line of code. Thanks, --CapitalR 18:41, 1 September 2007 (UTC)

Done. Kirill 18:53, 1 September 2007 (UTC)

Refresh to update templates

template:US Revolutionary units has been updated so that it actually follows the guidelines given for navbox layout (as opposed to pretending to be a campaign box). But because this article is fully-protected, the version transcluded here is out of date. The page needs to be refrehsed to pick up the template updates. Chris Cunningham 14:47, 24 October 2007 (UTC)

The documentation is actually at Wikipedia:WikiProject Military history/Military navigation, which isn't protected. In any case, though, I've removed the hard-coded example; since both templates now use the same layout, there's no need to show both of them here. Kirill 15:17, 24 October 2007 (UTC)

Alternative parameter name, missing parameters

Hi. Please help this template resemble and work alongside {{Navbox}} more closely by:

• including name as an alternative name for raw_name;
• boosting the font-size used for groupnames by 10% (i.e. to 110% its current setting);
• including the groupstyle, liststyle, abovestyle, belowstyle parameters offered by {{Navbox}}.

Thanks. Sardanaphalus (talk) 10:26, 2 April 2008 (UTC)

In order:

1. Done.
2. Done.
3. Will not be done. The entire point of this template is to have a single style for everything using it; allowing style overrides on a per-transclusion basis would make it largely pointless.

Kirill 11:35, 2 April 2008 (UTC)

• Okay, understood. Thanks for 1 and 2. Sardanaphalus (talk) 13:09, 5 April 2008 (UTC)

  PS I guess for consistency's sake this template could/should be renamed "Military navbox"?

I would support the rename, but wouldn't that mean going through every transclusion and changing "military navigation" to "military navbox"? That would take a while. bahamut0013♠♣ 14:17, 5 April 2008 (UTC)

excess white bar when hidden

I've noticed with a few different templates that is you utilize the |image= code, it has a tendancy to add a white bar at the bottom of the nabox when collapsed. Any idea what causes this? It looks funny when stacked with normal navboxes. See Template:US Navy navbox for example. bahamut0013♠♣ 11:40, 5 April 2008 (UTC)

Not sure, but I would guess that it's something with how the basic {{navbox}} handles images in certain cases, since this template doesn't do anything with the image parameters other than passing them straight through. Kirill 15:55, 5 April 2008 (UTC)

Military navigation vs {{navbox}}

What does this template provide over the {{navbox}} family of templates? The only visual difference seems to be a variation in colors in the overall heading row. See John_Branch#Sources for a comparision and see {{USSecNavy}} for a diff between the two. If it is just the autocategorization into the wikiproject, wouldn't it make more sense to use the {{navbox}} and just add cats to that? My curious 2c. — MrDolomite • Talk 09:43, 31 July 2008 (UTC)

• I think the main point of the template has less to do with categorization and more to do with a standardized look and feel for military articles. Much like {{Navbox musical artist}} and other similar templates, this one forces a standard color scheme and size to ensure the military boxes look the same and line up with each other. This template actually uses {{Navbox}} under the hood, so it is basically in the same template family. --CapitalR (talk) 12:53, 31 July 2008 (UTC)

Yep. While I'm all for standardisation, insofar as this is just a custom derivation of {{navbox}} it's perfectly fitting with that. I'd rather that people dispensed with it and just created navboxen with class="military-navigation" or whatever, but that's really just syntactical bickering. Chris Cunningham (not at work) - talk 13:17, 31 July 2008 (UTC)

Yes, the main use of this isn't the color, but rather the size+alignment needed to make things stack with the various standard military infoboxes. That's not really visible in {{USSecNavy}}, since that's set to be a full-width box; but compare, for example, {{Normandy battle beaches}}. Kirill ^(prof) 20:27, 31 July 2008 (UTC)

If color isn't a major consideration, why not remove the "wide" option and opt for using {{navbox}} directly when it is being used as a normal "wide" navbox at the bottom of the page? ~ Paul^T+/_C 00:05, 7 January 2009 (UTC)

He siad that "the main use of this isn't the color", which doesn't mean that color isn't a major consideration; it's just not the main consideration. It is important to maintain some level of standardization or consistancy in templates. This navbox, when used with the wide parameter, achieves just that: consistancy. As CapitalR said, it's good to have a "standardized look and feel for military articles". bahamut0013^words_deeds 13:01, 7 January 2009 (UTC)

15 groups

Why only 15 groups allowed? JonCatalán^(Talk) 05:51, 16 December 2008 (UTC)

Because nobody has asked to have more before. ;-)

(Luna Santin has fixed the template to support up to 20 groups now; if we need more, I think we'll need to add them to {{navbox}} first, and then expose them here.) Kirill ^(prof) 13:31, 16 December 2008 (UTC)

Thank you both! JonCatalán^(Talk) 15:18, 16 December 2008 (UTC)

"imageleft" field?

Does this template support the "imageleft" field available in Template:Navbox? In my attempt at converting Template:Sydney-Kormoran to use Template:Military navigation, "imageleft" seemed not to work. — Bellhalla (talk) 04:53, 20 August 2009 (UTC)

The template wasn't passing through that parameter to {{navbox}}. I've updated the code to do so; does that seem to work correctly? Kirill ^[talk] [pf] 12:48, 21 August 2009 (UTC)

That looks good. Thanks! — Bellhalla (talk) 17:52, 21 August 2009 (UTC)

Additional groups

I'm trying to break out and alphabetize the Cold War Figures infobox, can someone bump up the group count to 50? - Burpelson AFB ✈ 18:18, 30 August 2011 (UTC)

• This template is backed by {{Navbox}}, which only supports 20 groups/lists (for technical reasons, this cannot really be increased). Is it necessary to have more than 20 for your template? I'm guessing that when you alphabetize the names, not all of the letters will be used. If you still need more, I can help you get around the limit using {{Navbox subgroup}}. --CapitalR (talk) 22:28, 30 August 2011 (UTC)
  • After I alphabetized by country name it came out to 49. Have a look at User:Burpelson_AFB/sandbox, take out the nowiki tags and show preview. - Burpelson AFB ✈ 15:12, 31 August 2011 (UTC)

Edit request on 2 February 2012

please make this update to allow for the use of border parameter in navbox. This will allow this template to be nested, in the same way that navbox can be nested using the {{navbox|border=child}} construct. once this is done, it would be great if we could do the same for template:campaign. I am trying to clean up the nesting in Template:Campaignbox Iraq War. thank you. Frietjes (talk) 19:59, 2 February 2012 (UTC)

 Done -- WOSlinker (talk) 21:15, 2 February 2012 (UTC)

Better emulation of {{Navbox subgroup}} and {{Navboxes}}

I would like to get some changes for better flexibility:

1. To better allow subgrouping (or emulation of {{Navbox subgroup}})
   1. correct the passing of |title= so it defaults to nothing (so I do not have to override it to empty in things like {{WWIIJapaneseShips}})
   2. pass |evenodd=
   3. allow |border= to take on the value of "subgroup" as well as "child" (so |border=subgroup works)
2. To better allow encapsulation (or emulation of {{Navboxes}})
   1. pass |listpadding= and |liststyle= (so I can use {{Military navigation}} directly do not have to use {{navboxes}} or {{navbox}} with {{WPMILHIST Infobox style}} to emulate it in things like {{WWIIBritishAFVs}} and {{WWIISovietAFVs}})

Note: |style= still has to be passed to subgroups for things like |style=wide. I am not sure if there is a better method for this.

Thank you. 50.53.15.51 (talk) 20:05, 27 February 2012 (UTC)

I believe I have now implemented these changes within the sandbox, however, cannot create the sandbox (IPs cannot create new pages) to test such but with testing such can be copied straight form the sandbox at your discretion. Thanks again. 50.53.15.51 (talk) 20:38, 27 February 2012 (UTC)

Sounds good, but I'm cautious about pushing this without thorough testing. I've created template:military navigation/testcases if you want to add tests there. Thanks for your work on this. Chris Cunningham (user:thumperward) (talk) 15:28, 29 February 2012 (UTC)

I've disabled {{editprotected}} for now. Add it back when you're done testing. Tra (Talk) 16:30, 2 March 2012 (UTC)

Edit request on 16 October 2013

please change

|title={{{title}}}

to

|title={{{title|}}}

or (if there is a reason why we need to make |title= mandatory most of the time)

|title={{#ifeq:{{{border|}}}|child|{{{title|}}}|{{{title}}}}}

which will allow me to remove the blank |title= from the child box in Template:Shenandoah class destroyer tender. thank you. Frietjes (talk) 16:20, 16 October 2013 (UTC)

Done. Kirill ^[talk] 01:29, 17 October 2013 (UTC)

Edit request on 21 October 2013 - add groups/lsits

Please add the capability for additional groups/lists (going from 20 to 30 should be enough). This is to accomodate some ship classes that have more than 20 adiitional operators.

Example code:
...
|group18=
|list18=
|group19=
|list19=
|group20=
|list20=
|group21=
|list21=
|group22=
|list22=
|group23=
|list23=
|group24=
|list24=
|group25=
|list25=
|group26=
|list26=
|group27=
|list27=
|group28=
|list28=
|group29=
|list29=
|group30=
|list30=
...
|list18style=
|list19style=
|list20style=
|list21style=
|list22style=
|list23style=
|list24style=
|list25style=
|list26style=
|list27style=
|list28style=
|list29style=
|list30style=
...

Thank you.
Derekbridges (talk) 05:18, 21 October 2013 (UTC)

 Done Ruslik_Zero 19:29, 21 October 2013 (UTC)

raw_name to omit {{navbar}}?

I happened to come across the use of this template parameter at {{Military of Croatia}}. In that case, it was completely misplaced, because there was no obvious reason to do so. Fixing it was also very unintuitive, because "raw_name == no navbar" is not something any editor should be expected to remember. What is the actual purpose of this weirdly named parameter, and can we make it not so horrible? --Joy [shallot] (talk) 13:44, 14 August 2021 (UTC)

hlist considerations

I am currently working on moving Things to TemplateStyles (see MediaWiki_talk:Common.css/to_do) and right now I'm working on the hlist class. I'm planning to always emit it when the use here is as a campaign box (per the note at MediaWiki_talk:Common.css/to_do#Hlist_modules).

However, it would be easier for me, and I think ultimately more consistent with its uses and with the rest of the wiki, for campaign boxes to be {{sidebar}}s instead of navboxes. This would also change the change to be made here to use sidebar for generating the 'non-wide' version instead of always emitting the TemplateStyles.

Soliciting opinions on this before I get started on changing this over. The colors particularly I am sure will be a discussion point. Izno (talk) 23:40, 10 March 2022 (UTC)

Request for deletion

I would like to propose that this template be deleted. It seems to add no value over and above the standard navbox template other than a different colour scheme of blue and grey, which has at best an extremely tenuous link to the concept of a military. Elshad (talk) 12:56, 18 February 2023 (UTC)

 Not edited. The correct venue for what you want is WP:TFD. Since this template is used as a wrapper or shell for other military navbars, a deletion proposal will probably be met with a lot of opposition. Up to you, and thank you very much for your contributions! P.I. Ellsworth , ed. ^{put'er there} 17:02, 18 February 2023 (UTC)