Template talk:Navbox generic/Archive 3

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

problems with the navbox

I'm trying to make columns inside {{S.E.S. albums}}. It looks fine when you click the template page, but when you go to the article page, the left columns are bloated. Pandacomics 19:39, 11 July 2007 (UTC)

This is a Firefox issue, where it reflows (I'm guess that's what it's called) the dialog. I'll convert it to regular collapsible table and it'll also be better for accessibility (since your faking columns). —Dispenser 20:19, 29 July 2007 (UTC)

Does anyone know how to change the colors of the links

Simple question, but can anyone know the magic CSS incarnations to change the colors of the linked text (normal and visited) within the navbox. The defaults are difficult to see with some backgrounds colors in the navboxes. -- KelleyCook 17:03, 2 August 2007 (UTC)

This is one way: [[article|<span style="color:#129856;">text</span>]] produces text. –Pomte 05:45, 4 August 2007 (UTC)

Negate {{Tnavbar}}

I want to convert a footer to {{Navbox generic}} but the other editors do not want the {{Tnavbar}} included. Is there some way to negate that feature on this navbox, and if so please provide the code.--Old Hoss 02:09, 8 August 2007 (UTC)

I added an option to exclude this template. You can use '|navbar=plain' to not show the Tnavbar links. --CBD 10:57, 8 August 2007 (UTC)
Cool! One minor hitch is the centering of the title. With the Tnavbar present, the title centers properly between "v·d·e" and "[show/hide}". With the Tnvabr absent, the title is centered between the left margin and "[show/hide}", which throws it off a bit to the left. If this is not an easy fix, then don't fret over it too much - it's just aesthetics.
I did have another request:
  • Can the oddstlye and evenstyle also be set for the groupstyle? Currently the oddstlye and evenstyle can only be set for the liststyle. I wanted to alternate the group backgrounds to coincide with the alternating list backgrounds. If there is someway of doing this already, please provide the code.
I also have a suggestion:
  • Related to the below option, can new options be created for Wiktionary, Wikibooks, Wikiquote, Wikisource, Commons, Wikinews, Category, Project, and Portal? This would produce the following:
Regards.--Old Hoss 16:35, 8 August 2007 (UTC)
Please revert this change as it violates WP:OWN as previously discussed. —Dispenser 19:21, 8 August 2007 (UTC)
Eh? I see no such previous discussion on this talk page or its archives and don't see how an optional template parameter could possibly violate 'WP:OWN'... which is a policy about people who are not allowing changes to articles. --CBD 11:56, 9 August 2007 (UTC)

I was confused over the WP:OWN accusation as well, since that is probably the issue I try to be aware of the most. Looking at User:Dispenser's pages, I think it has something to do with the Tnavbar, but I in no way intended to remove or alter anything, only have the option of turning it off. I believe the post was in haste. Either way, hopefully we can proceed. Can my request to add the oddstlye and evenstyle parameter also be set for the groupstyle? I want to be able to alternate the colors blue and gray on the US Civil War template for both the groupstyle and liststyle. Regards.--Old Hoss 15:52, 9 August 2007 (UTC)

Sorry it wasn't discussed on this page but on Template talk:Dynamic navigation box. The problem is that removing this mechanism hinders others from editing the template. Thus a violation WP:OWN (which applies to all namespaces, btw) as it raises the bar of entry more and thus those editors posses a certain degree of ownership. This inaccessibility has even been directly suggested by some as reason to remove the v-d-e functionality. Now some may argue that they would like to use this template in userspace and this is a ask lost but I believe that other editors will agree with me that templates should stay in template space. (On a side note I think I just figured out how to fix the tnavbar problem.)Dispenser 05:10, 10 August 2007 (UTC)
It is true that no page in Wikipedia is 'owned' by anyone, but equally true that while articles may be extensively rewritten someone trying to do the same to another person's user page without very good reason is going to get stomped. There are different degrees of applicability. In this case, you are essentially saying that not having template view/edit buttons limits the ability to access the templates to people who understand how they work. I'm not sure that is entirely a bad thing and it certainly isn't a WP:OWN violation. No one is trying to keep the template from being edited when they don't manually insert an edit link into it. The template can still be edited in exactly the same way as thousands of other templates on Wikipedia that have no 'edit' link on them. This is no more an 'ownership' issue than the templates which are protected and can only be edited by admins... because those templates do still get changed. No one is trying to prevent that or claiming ownership.
I could make a better case for a 'WP:OWN' violation in the attempt to force users to always include Tnavbar. :] That is an example of trying to define how something must look and not allowing others to change it. --CBD 10:19, 10 August 2007 (UTC)

Template nowraplinks

Hi everyone. I have made a template and some CSS code that prevents word wraps inside links and only allows word wraps between the links and in normal text. This is useful for instance for long link lists. I am pretty sure this will be used in navigation boxes like {{Navbox generic}}. If any of you are interested I have brought my template and CSS code up for discussion at the village pump. See also {{nowraplinks}} itself and its talk page. --David Göthberg 15:34, 10 August 2007 (UTC)

Requested changes to cut size, delete deprecated parameters, add nowrap, fix bug with image placement

{{editprotected}}

I am requesting that the complete code for this template be changed to the following. The changes being made and the reasons for doing so are explained below.

New code

<table class="navbox collapsible {{{state|autocollapse}}}" style="margin:auto; {{{style|}}}{{{bodystyle|}}}">
<tr><!--

---Titlebar---
--><th colspan="{{#if:{{{image|}}}|3|2}}" style="text-align:center;width:100%;{{{titlestyle|}}}"><!--
--><div style="float:left; width:6em; text-align:left;">{{#switch:{{{navbar|}}} |plain= |#default={{Tnavbar|{{{name<noinclude>|Navbox generic</noinclude>}}} |mini=1}}}}</div><span style="font-size:110%;">{{{title}}}</span></th>
</tr><!--

---Above (optional)---
-->{{#if:{{{above|}}} |<tr><td style="{{{abovestyle|}}}" colspan="{{#if:{{{image|}}}|3|2}}">{{{above|}}}</td></tr>}}<!--

---Groups---
-->{{#if:{{{list1|}}}|<tr>{{#if:{{{group1|}}}|<th style="white-space:nowrap;{{{groupstyle|}}}">{{{group1}}}</th>}}
<td style="width:100%;{{{liststyle|}}}{{{oddstyle|}}}" colspan="{{#if:{{{group1|}}}|1|2}}">{{{list1}}}</td><!--

-->{{#if:{{{image|}}}|<td rowspan="{{#expr: {{#if:{{{list1|}}}|1|0}} +{{#if:{{{list2|}}}|1|0}} +{{#if:{{{list3|}}}|1|0}} +{{#if:{{{list4|}}}|1|0}} +{{#if:{{{list5|}}}|1|0}} +{{#if:{{{list6|}}}|1|0}} +{{#if:{{{list7|}}}|1|0}} +{{#if:{{{list8|}}}|1|0}} +{{#if:{{{list9|}}}|1|0}} +{{#if:{{{list10|}}}|1|0}} +{{#if:{{{list11|}}}|1|0}} +{{#if:{{{list12|}}}|1|0}} +{{#if:{{{list13|}}}|1|0}} +{{#if:{{{list14|}}}|1|0}} +{{#if:{{{list15|}}}|1|0}} +{{#if:{{{list16|}}}|1|0}} +{{#if:{{{list17|}}}|1|0}} +{{#if:{{{list18|}}}|1|0}} +{{#if:{{{list19|}}}|1|0}} +{{#if:{{{list20|}}}|1|0}}}}" <!--
-->style="vertical-align:middle; padding-left:7px; width:0%; {{{imagestyle|}}}">{{{image}}}</td>}}</tr>}}<!--

-->{{#if:{{{list2|}}}|<tr>{{#if:{{{group2|}}}|<th style="white-space:nowrap;{{{groupstyle|}}}">{{{group2}}}</th>}}
<td style="width:100%;{{{liststyle|}}}{{{evenstyle|}}}" colspan="{{#if:{{{group2|}}}|1|2}}">{{{list2}}}</td></tr>}}<!--

-->{{#if:{{{list3|}}}|<tr>{{#if:{{{group3|}}}|<th style="white-space:nowrap;{{{groupstyle|}}}">{{{group3}}}</th>}}
<td style="width:100%;{{{liststyle|}}}{{{oddstyle|}}}" colspan="{{#if:{{{group3|}}}|1|2}}">{{{list3}}}</td></tr>}}<!--

-->{{#if:{{{list4|}}}|<tr>{{#if:{{{group4|}}}|<th style="white-space:nowrap;{{{groupstyle|}}}">{{{group4}}}</th>}}
<td style="width:100%;{{{liststyle|}}}{{{evenstyle|}}}" colspan="{{#if:{{{group4|}}}|1|2}}">{{{list4}}}</td></tr>}}<!--

-->{{#if:{{{list5|}}}|<tr>{{#if:{{{group5|}}}|<th style="white-space:nowrap;{{{groupstyle|}}}">{{{group5}}}</th>}}
<td style="width:100%;{{{liststyle|}}}{{{oddstyle|}}}" colspan="{{#if:{{{group5|}}}|1|2}}">{{{list5}}}</td></tr>}}<!--

-->{{#if:{{{list6|}}}|<tr>{{#if:{{{group6|}}}|<th style="white-space:nowrap;{{{groupstyle|}}}">{{{group6}}}</th>}}
<td style="width:100%;{{{liststyle|}}}{{{evenstyle|}}}" colspan="{{#if:{{{group6|}}}|1|2}}">{{{list6}}}</td></tr>}}<!--

-->{{#if:{{{list7|}}}|<tr>{{#if:{{{group7|}}}|<th style="white-space:nowrap;{{{groupstyle|}}}">{{{group7}}}</th>}}
<td style="width:100%;{{{liststyle|}}}{{{oddstyle|}}}" colspan="{{#if:{{{group7|}}}|1|2}}">{{{list7}}}</td></tr>}}<!--

-->{{#if:{{{list8|}}}|<tr>{{#if:{{{group8|}}}|<th style="white-space:nowrap;{{{groupstyle|}}}">{{{group8}}}</th>}}
<td style="width:100%;{{{liststyle|}}}{{{evenstyle|}}}" colspan="{{#if:{{{group8|}}}|1|2}}">{{{list8}}}</td></tr>}}<!--

-->{{#if:{{{list9|}}}|<tr>{{#if:{{{group9|}}}|<th style="white-space:nowrap;{{{groupstyle|}}}">{{{group9}}}</th>}}
<td style="width:100%;{{{liststyle|}}}{{{oddstyle|}}}" colspan="{{#if:{{{group9|}}}|1|2}}">{{{list9}}}</td></tr>}}<!--

-->{{#if:{{{list10|}}}|<tr>{{#if:{{{group10|}}}|<th style="white-space:nowrap;{{{groupstyle|}}}">{{{group10}}}</th>}}
<td style="width:100%;{{{liststyle|}}}{{{evenstyle|}}}" colspan="{{#if:{{{group10|}}}|1|2}}">{{{list10}}}</td></tr>}}<!--

-->{{#if:{{{list11|}}}|<tr>{{#if:{{{group11|}}}|<th style="white-space:nowrap;{{{groupstyle|}}}">{{{group11}}}</th>}}
<td style="width:100%;{{{liststyle|}}}{{{oddstyle|}}}" colspan="{{#if:{{{group11|}}}|1|2}}">{{{list11}}}</td></tr>}}<!--

-->{{#if:{{{list12|}}}|<tr>{{#if:{{{group12|}}}|<th style="white-space:nowrap;{{{groupstyle|}}}">{{{group12}}}</th>}}
<td style="width:100%;{{{liststyle|}}}{{{evenstyle|}}}" colspan="{{#if:{{{group12|}}}|1|2}}">{{{list12}}}</td></tr>}}<!--

-->{{#if:{{{list13|}}}|<tr>{{#if:{{{group13|}}}|<th style="white-space:nowrap;{{{groupstyle|}}}">{{{group13}}}</th>}}
<td style="width:100%;{{{liststyle|}}}{{{oddstyle|}}}" colspan="{{#if:{{{group13|}}}|1|2}}">{{{list13}}}</td></tr>}}<!--

-->{{#if:{{{list14|}}}|<tr>{{#if:{{{group14|}}}|<th style="white-space:nowrap;{{{groupstyle|}}}">{{{group14}}}</th>}}
<td style="width:100%;{{{liststyle|}}}{{{evenstyle|}}}" colspan="{{#if:{{{group14|}}}|1|2}}">{{{list14}}}</td></tr>}}<!--

-->{{#if:{{{list15|}}}|<tr>{{#if:{{{group15|}}}|<th style="white-space:nowrap;{{{groupstyle|}}}">{{{group15}}}</th>}}
<td style="width:100%;{{{liststyle|}}}{{{oddstyle|}}}" colspan="{{#if:{{{group15|}}}|1|2}}">{{{list15}}}</td></tr>}}<!--

-->{{#if:{{{list16|}}}|<tr>{{#if:{{{group16|}}}|<th style="white-space:nowrap;{{{groupstyle|}}}">{{{group16}}}</th>}}
<td style="width:100%;{{{liststyle|}}}{{{evenstyle|}}}" colspan="{{#if:{{{group16|}}}|1|2}}">{{{list16}}}</td></tr>}}<!--

-->{{#if:{{{list17|}}}|<tr>{{#if:{{{group17|}}}|<th style="white-space:nowrap;{{{groupstyle|}}}">{{{group17}}}</th>}}
<td style="width:100%;{{{liststyle|}}}{{{oddstyle|}}}" colspan="{{#if:{{{group17|}}}|1|2}}">{{{list17}}}</td></tr>}}<!--

-->{{#if:{{{list18|}}}|<tr>{{#if:{{{group18|}}}|<th style="white-space:nowrap;{{{groupstyle|}}}">{{{group18}}}</th>}}
<td style="width:100%;{{{liststyle|}}}{{{evenstyle|}}}" colspan="{{#if:{{{group18|}}}|1|2}}">{{{list18}}}</td></tr>}}<!--

-->{{#if:{{{list19|}}}|<tr>{{#if:{{{group19|}}}|<th style="white-space:nowrap;{{{groupstyle|}}}">{{{group19}}}</th>}}
<td style="width:100%;{{{liststyle|}}}{{{oddstyle|}}}" colspan="{{#if:{{{group19|}}}|1|2}}">{{{list19}}}</td></tr>}}<!--

-->{{#if:{{{list20|}}}|<tr>{{#if:{{{group20|}}}|<th style="white-space:nowrap;{{{groupstyle|}}}">{{{group20}}}</th>}}
<td style="width:100%;{{{liststyle|}}}{{{evenstyle|}}}" colspan="{{#if:{{{group20|}}}|1|2}}">{{{list20}}}</td></tr>}}<!--

---Below (optional)---
-->{{#if:{{{below|}}}|<tr><td style="{{{belowstyle|}}}" colspan="{{#if:{{{image|}}}|3|2}}">{{{below|}}}</td></tr>}}<!--

--></table><noinclude><!--

-->{{{{FULLPAGENAME}}/doc}}
<!-- Add cats and interwikis to the /doc subpage, not here! -->
</noinclude>

The reasons for the changes

  • Cuts down the template size. I've been running into problems with this template simply being too big in some articles, causing the pre-expand limit to be reached and pages to only partially load (see Wikipedia:Template limits). These changes cut the size from 10k to 6.5k, which will help out a little bit.
  • Deletes all deprecated parameters from the template. I recently went through all 4000 templates that transclude this one and converted every single deprecated parameter to the correct parameter (see my edit history, I made about 1200 edits to templates to accomplish this task).
  • Adds the "white-space:nowrap" style to the groups. This was a major problem in lots of instances of this template; the groups were being made much too large by accident. This will correct the problem.
  • Fixes a problem with image placement when no groups are specified and the lists are small (the image would be place away from the right side of the template, instead of against the right side like it should be fixed). This was fixed by forcing the list width to be as large as possible to force the image to the side.
  • The general appearance of the template is not changed at all by this edit (only the minor group size and image placement bugs are fixed). The major reason for this edit is to cut the template size.

Examples of these changes in use

See User:CapitalR/Test for a version of this template with the changes implemented. See User:CapitalR/Test3 for lots of templates using this new version (to prove that the changes actually work). It has been tested on IE, Firefox, Safari, and Opera on a few hundred instances of templates, and no errors have been found.

Summary

Please let me know if there are any problems or questions. Thanks, --CapitalR 05:10, 11 August 2007 (UTC)

Done. Cheers. --MZMcBride 05:40, 11 August 2007 (UTC)
Thanks -CapitalR 22:08, 12 August 2007 (UTC)

Why this template?

I notice that many of the "Navbox" templates are being replaced with "Navbox_generic". I might be a minority in this, but I think that this template is awful when it is hidden and opened on most articles. By default, they usually show up as small rectangles, but then when you open them, they explode to encompass the full width of the page; then when you close them, they go back to the small rectangle state. This is an example. I find the behaviour to be atrocious in terms of navigation, especially when you have to click "show" twice to open them. So, unless this has become standard procedure, I want to know why the switch to such a poorly-coded template, and if there's any way to either fix it so the dwonky behavior can stop. --Toussaint 22:40, 11 August 2007 (UTC)

Hi, I'm afraid I can't tell you why many {{navbox}} templates are being replaced with {{navbox Generic}} (you should find the editors doing this and ask them on their talk pages), but I can tell you how the size problem could be fixed. It sounds to me as if your major problem is with the change in the width of the template between when it's collapsed versus expanded, in which case the easiest fix would be to add width:100% to the table CSS. This should force the table to be as wide as possible regardless of whether it's expanded or collapsed; however, it may cause problems with custom width settings, depending on how it's implemented. Of course, this only describes the fix, it's not a declaration of my own opinion of the behavior, nor is it saying that everyone (or even a majority of people) agree with you. As far as clicking some templates twice to open them is concerned, I'd appreciate a link to an example, as your example above doesn't exhibit that behavior. --Dinoguy1000 Talk 01:16, 12 August 2007 (UTC)
  • The problem was with a change I made a few days ago on this template to correct for problems of image placement in the template (which had the unintended consequence of causing problems when the width:auto; style tag is used). Even adding the width:100% code would not fix it, as the problem arises when users of this template add the width:auto; to the style. The width:auto would override any width:100% that we add to the main template. I'll fix this problem by locating and correcting instances of the width:auto in all sub-templates in the next 24 hours (I'm downloading the latest database dump right now; after that's done I'll just do a quick search to find all the templates that exhibit this problem and fix them quickly). Sorry for the inconvenience. --CapitalR 19:36, 12 August 2007 (UTC)
    • Ok, all fixed. --CapitalR 00:29, 13 August 2007 (UTC)

Problem with style="width:auto"

Ever since the latest change to this template, every template that uses this one and has the style="width:auto" set, is not working. Here is an example Template:Apple. The strange part is that it still works when the templates are collapsed but not when expanded.

Very weird. I'll go through and fix this later today / tomorrow. Sorry for the problems. --CapitalR 18:33, 12 August 2007 (UTC)
Ok, all fixed I think. --CapitalR 00:29, 13 August 2007 (UTC)
Up until a couple days ago, "width:auto" displayed the template wrapping around the text. Now it extends to 100%. Is there some way I can get the template be no larger than the amount of text? --thedemonhog talkedits 03:38, 13 August 2007 (UTC)