![]() | This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 10 | ← | Archive 14 | Archive 15 | Archive 16 | Archive 17 | Archive 18 | → | Archive 20 |
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Hello,
I encountered these orphan parentheses.
Look at these screen photos :
I like the spaces in the parentheses, but these orphan parentheses are not nice typography. Please replace the spaces with non-breaking spaces, so that every parenthesis be on the good line.
Thanks,
-- Nnemo ( talk) 21:45, 25 February 2012 (UTC)
Hi there, I was looking at Template:Mongol Empire, and noticed some spurious spaces in "( see also House of Ogedei )". I went to remove them, but it seems they are auto-generated by the template. The relevant lines are:
* [[Chagatai Khanate]] ** see also [[House of Ogedei]]
Whatever I do to try to close up the whitespace in the source, the spaces still incorrectly appear in the output. I assume, therefore, that this is a bug in the "navbox" template itself. Regards, 86.177.105.189 ( talk) 03:11, 14 February 2012 (UTC)
* [[Chagatai Khanate]] (see also [[House of Ogedei]])
* [[Chagatai Khanate]] (item 1 · item 2 · item 1)
<small>
inside navboxes that produces unreadable text (9px), as shown in the example above. I regard anything under 11px illegible, and some people even find that too small. It would be a good idea to make a note in
WP:ACCESS about font sizes. —
Edokter (
talk) —
15:26, 16 February 2012 (UTC)
Since some people do not like the space before and after the parenthesis causing potential line breaks, I thought I would suggest using a non-breaking space or adding style to it to force the whitespace to not break at that point. I am not sure how well that would work or lack thereof as the list delimiters are stuffed between the HTML list markup via CSS. I hope this helps. 50.53.15.51 ( talk) 17:02, 8 March 2012 (UTC)
Has a change been made to capital letters for V, T, E. It looks - well - wrong. I prefer lower case. -- Alan Liefting ( talk - contribs) 20:36, 24 February 2012 (UTC)
.navbar.mini li span { font-variant: normal; }
I also think the uppercase letters are too attention-grabbing. The lowercase worked much better, though we might also be able to reduce the font size to achieve a similar effect. Maybe. As for the edit links in article-space, I don't see much alternative. The minor confusion it might cause for non-editors is far outweighed by the convenience of editors; without the link, finding and editing the template is a multi-step process. Powers T 13:03, 9 March 2012 (UTC)
I've searched the Talk archives and the Help files to no avail, so I'm hoping someone here can help... I've recently created the navbox {{ Knots}}, to tie together (pun intended) articles on specific knots. However, articles with the template transcluded onto them (so far, that's only Adjustable bend and Albright special) now appear on the "What links here" list for all articles in the template. I've been asked if it's possible to prevent this from happening - as far as I can tell, it isn't, but this is the first time I've created a template and I'm very inexperienced with the markup elements used. Does anyone know of a way to prevent articles with a navbox template from showing up in the WLH list of every article in the navbox? Yunshui 雲 水 09:13, 1 March 2012 (UTC)
This edit appears to have caused the 2011 winners not to display. They're the 21st group; I'm guessing there's a 20-group limit. Is there a work-around? The issue will affect more such navboxes, as the years progress. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:38, 26 March 2012 (UTC)
Someone recently created a new navbox, Template:WikiProject Albums navbox. When used on some pages it's initially expanded, but on some other pages it starts out collapsed. I believe this is because a navbox defaults to state=autocollapsed, and the pages where it starts out collapsed have other collapsible tables. But I thought I could override that in an individual article by specifying state=uncollapsed when I use the navbox. I tried this at Wikipedia:WikiProject Albums/Album article style guide, but the navbox still starts out collapsed. What am I doing wrong? I tried changing the navbox itself to say state=autocollapsed, instead of letting it default to that, but, perhaps unsurprisingly, that didn't seem to make any difference. Thanks in advance for any help. P.S. If it makes any difference, I'm using Windows 7 and Firefox 11. — Mudwater ( Talk) 02:07, 29 March 2012 (UTC)
Is it possible to change the color of the hyperlinks in the title without having to resort to a span tag? TheBigJagielka ( talk) 17:00, 9 March 2012 (UTC)
{{
New York Yankees}}
(white font on black bg). When using <span> like: |title=<span style="color:white>[[New York Yankees]]</span>
, the color is not as intended (see sandbox
[1]). However, since the template uses |title=<font color=white">[[New York Yankees]]</font>
, the desired color is present, both in wikilink as in selflink situations. Note: shouldn't this be in the documentation somehow, near "titlestyle" and "groupstyle"? -
DePiep (
talk) 10:14, 19 April 2012 (UTC)Hello. Is it possible to re-create this template for other Wikipedias? E.g. the German Wikipedia, this template would be very useful. Because this is a very complex template, I'm really not able to do it by myself. – weltforce™ | ☣ Talk 12:35, 2 May 2012 (UTC)
I copied the Navbox and Navbar now into a German Wikipedia's sandbox and linked Navbar correctly to Navbox. But when I test the template, no navbox is coming up. Maybe class="navbox-group" is missing? Is is able to copy it? Thanks in advance – weltforce™ | ☣ Talk 16:09, 6 May 2012 (UTC)
Thanks a lot! Now working correctly. – weltforce™ | ☣ Talk 10:21, 7 May 2012 (UTC)
When bodyclass=hlist
, the
cite link labels do not work:
Markup | Renders as |
---|---|
{{Navbox | name= name | group1 = Group1 | list1 = <ref group=lower-alpha>reference</ref> | belowclass = | below = {{reflist|group=lower-alpha}}}} |
|
{{Navbox | name= name | bodyclass = hlist | group1 = Group1 | list1 = <ref group=lower-alpha>reference2</ref> | belowclass = | below = {{reflist|group=lower-alpha}}}} |
|
---— Gadget850 (Ed) talk 22:45, 11 May 2012 (UTC)
Among interlinks, you should add it:Template:Navbox generic.-- Mauro Tozzi ( talk) 07:57, 5 June 2012 (UTC)
Hello! I wonder how the feature "hlist" works. If I'm not wrong, "hlist" converts lists like this
* List1 * List2 * List3
into
List1 • List2 • List3
My question is: how does that work? Thanks!-- Weltforce ( talk) 19:31, 16 June 2012 (UTC)
This is a minor style issue but many (well ok I know of three!) editors like to place a blank line between the footer templates and the text above it. Is it feasible to add a bit of code into the template that gives the option of placing a half or full line space above the template? It will give a slight improvement in readability. Mobile devices will have to be treated separately. There has been at least one silly debate and edit war about it. See Talk:Reach for the Sky. If is is technically feasible I will bring it up as a WP:MOS discussion. -- Alan Liefting ( talk - contribs) 23:05, 16 June 2012 (UTC)
I'm having difficulty getting a box to be collapsed by default. Is it enough to write "state=collapsed", or is something more needed? SlimVirgin (talk) 21:53, 17 June 2012 (UTC)
I am ready to add a 21st list, or frankly go up to 30. {{ MARepresentatives}} could really use it. A very simple addition to the code which would have no harm. Please advise.— GoldRingChip 12:48, 29 June 2012 (UTC)
a • b • c
becomes
* a * b * c
but the output still looks the same. Makes it easier to edit lists, especially if you want to sort them. -- WOSlinker ( talk) 14:28, 29 June 2012 (UTC)
For templates like {{
MNAC}}, whose title is not in English, it would be useful to have a |title_lang=
, to take a two-letter ISO code for the relevant language, with output comparable to |native_name_lang=
in {{
Infobox person}}.
Andy Mabbett (Pigsonthewing);
Talk to Andy;
Andy's edits
19:31, 17 July 2012 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Two things here: First, Tidy isn't required if someone wants to import this template to another wiki; I have successfully imported and used {{
Navbox}}
on several wikis without Tidy, without having to modify the template at all, so the notices stating that Tidy is required should probably be removed (this does not require an admin, and is therefore not part of the edit request; I'm just looking for consensus or caveats that I'm unaware of).
Second (and, I suppose, actually a counterpoint to my first comment =D ), if Navbox is used together with the hlist class on wikis without Tidy, it has some caveats that must be worked around (
bugzilla:39066). While I still haven't figured out the wrapping bug (would anyone more familiar with the CSS for Navbox and hlists like to have a crack at that one?), the broken HTML can be fixed by closing tags on the line following the {{{listN}}}
markup instead of on the same line, as seen
here. This change doesn't have any adverse side effects as far as I can tell, so could it be done here on Wikipedia as well, so other reusers won't have to worry about this? 「
ディノ奴
千?!」
? ·
☎ Dinoguy1000
21:45, 6 August 2012 (UTC)
Spacing things in this template can cause unnecessary paragraph tags to show up, so that would be something to double check. The other thing that could be a problem is all of this in context of the family of navbox templates (with columns, subgroup, etc.).
On Tidy, that can be edited via template:navbox/doc per the usual editing process. I've turned off the notice until those other test cases are checked and there's a consensus. -- Izno ( talk) 23:03, 6 August 2012 (UTC)
{{{above}}}
(and, therefore, probably also {{{below}}}
) causes a paragraph tag to be added, which changes the padding and line-height. I wouldn't be surprised if paragraph tags are also being added to the listN
's, but if so, they're not changing anything visually. They also don't seem to affect child navboxes; the first navbox
here uses child navboxes to display the subheaders and subsequent groups/lists, with no change in padding or spacing (except the previously noted above
. 「
ディノ奴
千?!」
? ·
☎ Dinoguy1000
23:17, 6 August 2012 (UTC)People keep putting release years in brackets following films in navboxes – an example:
This strikes me as being curious and unnecessary. Dates aren't put after albums, books, etc. in navboxes, so why should this be an exception? I think it would be good if we could come to a consensus on this.
On another note, I also think these group classings are unnecessary, given that there are only six films here, and that it would look neater and simpler without them. Lachlan Foley ( talk) 00:34, 16 September 2012 (UTC)
Does anyone know why this template is expanding beyond the width of the page? Thanks. Rangoon11 ( talk) 18:26, 21 September 2012 (UTC)
<!-- Served by mw28 in 0.137 secs. -->
</body>
</html>
Served by
" up to "secs.
", and paste it below. Then I can add the relevant server code to the bug report at
bugzilla:38273. Thanks. --
Redrose64 (
talk)
18:53, 21 September 2012 (UTC)
) is enough to trigger the error. —
Edokter (
talk) —
18:23, 23 September 2012 (UTC)With HTML5 enabled, this template now generates two validation errors due to the use of cellspacing
. See
[2], which is a validation of the sandbox without the doc page (which generates a lot of errors due to other templates). ---—
Gadget850 (Ed)
talk
12:20, 24 September 2012 (UTC)
Sorry if this has been brought up, but I just noticed hlist navboxes have an extra, pointless dot after the final item. Now that I've noticed it, I can't unnotice it. I think it might drive me insane. Even if it doesn't, it looks bad. Is there a good reason for it? If not, it should be fixed. Thanks. InedibleHulk ( talk) 02:22, 25 October 2012 (UTC)
I could ask a long, complicated question about this, but it would be simpler to ask whether what I am trying to do at User:Rrius/Userboxes can work. - Rrius ( talk) 00:35, 15 November 2012 (UTC)
<td style="width: 238px;">(the width specified in the userbox's code), and it didn't work. - Rrius ( talk) 02:36, 15 November 2012 (UTC)
Is there any special way to set the groupstyle? Please see the recent edit history of
Template:Middle-earth films where the group boxes did not accept the intended background colour. I've also experienced this problem last night when playing around with {{
Authority control}} in my user sandbox. It seems that contrary to what the documentation tells us, |groupstyle = background: foo;
doesn't work.
De728631 (
talk)
16:30, 18 November 2012 (UTC)
| groupstyle = {{#if|{{{embed|yes}}|background: white;}}}
but that didn't work, while I could easily set |listclass
that way.
De728631 (
talk)
20:51, 18 November 2012 (UTC)
Mismatching delimiters all over the place. {{#if:{{{embed|yes}}}|background: white;}}. Alternatively, you may be looking for {{#ifeq:{{{embed|yes}}}|yes|background: white;}}. Not sure.
That said, you should really avoid setting colors per WP:COLOR. (I would tend to argue the more extreme position that styling should not be allowed except widths, and even that only at the navbox level.) -- Izno ( talk) 20:58, 18 November 2012 (UTC)
Answers to the above are not explicit on Template:Navbox, although "navbar" appears 6 times in Template:Navbox with the 1st mention saying what a navbar parameter does. "See also" is does not say explicitly what the distinction is between navbar and sidebar either or what the respective links do. IMO they should be worked into a separate an earlier section, not concealed in "See also". Thanks. --
Thomasmeeks (
talk)
03:30, 8 December 2012 (UTC)
I noticed that this template creates 2px height blank rows to create gaps between the rows. this works, in most cases, but I have noticed a quirk, if you compare the following:
if you look, the second version has a spurious 2px gap at the top of the subgroups. of course, the easy solution for this is to simply not use high numbered group/list values without the low numbered ones. however, if you do DePiep will quickly revert your changes. so, it appears the only solution is to change this template. it would be nice to have the padding set using style statements, rather than blank rows, but I understand this is difficult to do with CSS (see, e.g., this thread)? I understand that we want to avoid introducing a bunch of new #if statements like we have for the first couple rows. any ideas? Frietjes ( talk) 17:22, 23 December 2012 (UTC)
evenodd = swap
), but today here you do not mention that and you propose to change the navbox template? -
DePiep (
talk)
19:28, 23 December 2012 (UTC)
group1=... | list1=...
.group1
} going wrong| evenodd = swap
. —
Edokter (
talk) —
18:38, 23 December 2012 (UTC)
oddstyle = background: transparent evenstyle = background: #f7f7f7;
|groupn=
|listn=
and none of these pairs are mandatory; nor is it required to use consecutive numbers (I have constructed navboxes that used rows 1-6 and 11-14, because the groupings fell into two distinct categories). I also fail to see why you would need to mess around with |oddstyle=
|evenstyle=
when we have |evenodd=swap
. --
Redrose64 (
talk)
21:49, 23 December 2012 (UTC)
|oddstyle=
|evenstyle=
- I agree. I just mentioned it to show the option, and I already noted that others had pointed to a better option. Still, it is a correct coding, documented and CSS & template consistent.|groupn=
|listn=
. I cannot help or correct your failing. Edokter has explained and demonstrated, in this thread, that using "group1" or "group2" solves the issue of: BOTH alternating grey/transparent bg AND prevent top padding 2px (gap).group1
or group2
prevents the 2px gap appearing. First group in a (sub)navbox template group3
or higher does introduce the 2px gap. Using n=1 or n=2 also allows steering the even/odd (transparent/grey) bg. All fine. So, acrtually it does matter where the sequence starts (1 and 2 good, 3 and up bad). That is what this thread is about. Other remarks (e.g. about setting a bg color) are illustratative or alternatives, interesting but not needed. -
DePiep (
talk)
23:05, 23 December 2012 (UTC)Please take a look at Wikipedia:Village pump (technical)#Navboxes and touch devices. Thanks, — This, that, and the other (talk) 09:28, 2 January 2013 (UTC)
Can someone help fix {{ Yugoslavia timeline}} so that it actually supports a {{ collapsible option}}? I tried the basic conversion, put all the content in navbox list1, but I get nothing rendered that way. See Template:Yugoslavia timeline/sandbox. -- Joy [shallot] ( talk) 10:28, 6 January 2013 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please replace the following line of the template's code (line 8)
--><table cellspacing="0" class="nowraplinks {{{bodyclass|}}} {{#if:{{{title|}}}|{{#switch:{{{state|}}}|<!--
... with ...
--><table cellspacing="0" class="nowraplinks {{{bodyclass|{{{class|}}}}}} {{#if:{{{title|}}}|{{#switch:{{{state|}}}|<!--
... in order to provide the alterative name class
for the bodyclass
parameter (complementing the style/bodystyle parameter; and as implemented in the Sidebar templates).
CsDix ( talk) 13:44, 13 February 2013 (UTC)
style
is already offered here as an alternative to bodystyle
and class/bodyclass
is already in use in Sidebars. Apologies if the above didn't make that sufficiently clear.
CsDix (
talk)
14:17, 13 February 2013 (UTC)
bodystyle
's alternative name (style
).
CsDix (
talk)
22:37, 13 February 2013 (UTC){{
edit protected}}
template. --
Redrose64 (
talk)
21:30, 13 February 2013 (UTC)![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please replace the line...
--><tr><td class="navbox-abovebelow {{{belowclass|}}}" style="{{{basestyle|}}};{{{belowstyle|}}}" <!--
...near the end of the code (in the "---Below---" section) with...
--><tr><td class="{{#ifeq:{{{belowclass|}}}|navbox-title | |navbox-abovebelow}} {{{belowclass|}}}" style="{{{basestyle|}}};{{{belowstyle|}}}" <!--
...to allow |belowclass=navbox-title
to override the default "navbox-abovebelow" class setting. (I believe – hope – this is simply an omission rather than something that requires consensus harvesting.)
CsDix ( talk) 00:57, 25 February 2013 (UTC)
Using "listclass=hlist hnum", numbered list appears on only list1. Is this an intent function? And if I want to show numbered list for all list2, list3, ..., what should I do? — Preceding unsigned comment added by Nullzero ( talk • contribs) 11:55, 24 February 2013 (UTC)
|
|
|
|
![]() | This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 10 | ← | Archive 14 | Archive 15 | Archive 16 | Archive 17 | Archive 18 | → | Archive 20 |
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Hello,
I encountered these orphan parentheses.
Look at these screen photos :
I like the spaces in the parentheses, but these orphan parentheses are not nice typography. Please replace the spaces with non-breaking spaces, so that every parenthesis be on the good line.
Thanks,
-- Nnemo ( talk) 21:45, 25 February 2012 (UTC)
Hi there, I was looking at Template:Mongol Empire, and noticed some spurious spaces in "( see also House of Ogedei )". I went to remove them, but it seems they are auto-generated by the template. The relevant lines are:
* [[Chagatai Khanate]] ** see also [[House of Ogedei]]
Whatever I do to try to close up the whitespace in the source, the spaces still incorrectly appear in the output. I assume, therefore, that this is a bug in the "navbox" template itself. Regards, 86.177.105.189 ( talk) 03:11, 14 February 2012 (UTC)
* [[Chagatai Khanate]] (see also [[House of Ogedei]])
* [[Chagatai Khanate]] (item 1 · item 2 · item 1)
<small>
inside navboxes that produces unreadable text (9px), as shown in the example above. I regard anything under 11px illegible, and some people even find that too small. It would be a good idea to make a note in
WP:ACCESS about font sizes. —
Edokter (
talk) —
15:26, 16 February 2012 (UTC)
Since some people do not like the space before and after the parenthesis causing potential line breaks, I thought I would suggest using a non-breaking space or adding style to it to force the whitespace to not break at that point. I am not sure how well that would work or lack thereof as the list delimiters are stuffed between the HTML list markup via CSS. I hope this helps. 50.53.15.51 ( talk) 17:02, 8 March 2012 (UTC)
Has a change been made to capital letters for V, T, E. It looks - well - wrong. I prefer lower case. -- Alan Liefting ( talk - contribs) 20:36, 24 February 2012 (UTC)
.navbar.mini li span { font-variant: normal; }
I also think the uppercase letters are too attention-grabbing. The lowercase worked much better, though we might also be able to reduce the font size to achieve a similar effect. Maybe. As for the edit links in article-space, I don't see much alternative. The minor confusion it might cause for non-editors is far outweighed by the convenience of editors; without the link, finding and editing the template is a multi-step process. Powers T 13:03, 9 March 2012 (UTC)
I've searched the Talk archives and the Help files to no avail, so I'm hoping someone here can help... I've recently created the navbox {{ Knots}}, to tie together (pun intended) articles on specific knots. However, articles with the template transcluded onto them (so far, that's only Adjustable bend and Albright special) now appear on the "What links here" list for all articles in the template. I've been asked if it's possible to prevent this from happening - as far as I can tell, it isn't, but this is the first time I've created a template and I'm very inexperienced with the markup elements used. Does anyone know of a way to prevent articles with a navbox template from showing up in the WLH list of every article in the navbox? Yunshui 雲 水 09:13, 1 March 2012 (UTC)
This edit appears to have caused the 2011 winners not to display. They're the 21st group; I'm guessing there's a 20-group limit. Is there a work-around? The issue will affect more such navboxes, as the years progress. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:38, 26 March 2012 (UTC)
Someone recently created a new navbox, Template:WikiProject Albums navbox. When used on some pages it's initially expanded, but on some other pages it starts out collapsed. I believe this is because a navbox defaults to state=autocollapsed, and the pages where it starts out collapsed have other collapsible tables. But I thought I could override that in an individual article by specifying state=uncollapsed when I use the navbox. I tried this at Wikipedia:WikiProject Albums/Album article style guide, but the navbox still starts out collapsed. What am I doing wrong? I tried changing the navbox itself to say state=autocollapsed, instead of letting it default to that, but, perhaps unsurprisingly, that didn't seem to make any difference. Thanks in advance for any help. P.S. If it makes any difference, I'm using Windows 7 and Firefox 11. — Mudwater ( Talk) 02:07, 29 March 2012 (UTC)
Is it possible to change the color of the hyperlinks in the title without having to resort to a span tag? TheBigJagielka ( talk) 17:00, 9 March 2012 (UTC)
{{
New York Yankees}}
(white font on black bg). When using <span> like: |title=<span style="color:white>[[New York Yankees]]</span>
, the color is not as intended (see sandbox
[1]). However, since the template uses |title=<font color=white">[[New York Yankees]]</font>
, the desired color is present, both in wikilink as in selflink situations. Note: shouldn't this be in the documentation somehow, near "titlestyle" and "groupstyle"? -
DePiep (
talk) 10:14, 19 April 2012 (UTC)Hello. Is it possible to re-create this template for other Wikipedias? E.g. the German Wikipedia, this template would be very useful. Because this is a very complex template, I'm really not able to do it by myself. – weltforce™ | ☣ Talk 12:35, 2 May 2012 (UTC)
I copied the Navbox and Navbar now into a German Wikipedia's sandbox and linked Navbar correctly to Navbox. But when I test the template, no navbox is coming up. Maybe class="navbox-group" is missing? Is is able to copy it? Thanks in advance – weltforce™ | ☣ Talk 16:09, 6 May 2012 (UTC)
Thanks a lot! Now working correctly. – weltforce™ | ☣ Talk 10:21, 7 May 2012 (UTC)
When bodyclass=hlist
, the
cite link labels do not work:
Markup | Renders as |
---|---|
{{Navbox | name= name | group1 = Group1 | list1 = <ref group=lower-alpha>reference</ref> | belowclass = | below = {{reflist|group=lower-alpha}}}} |
|
{{Navbox | name= name | bodyclass = hlist | group1 = Group1 | list1 = <ref group=lower-alpha>reference2</ref> | belowclass = | below = {{reflist|group=lower-alpha}}}} |
|
---— Gadget850 (Ed) talk 22:45, 11 May 2012 (UTC)
Among interlinks, you should add it:Template:Navbox generic.-- Mauro Tozzi ( talk) 07:57, 5 June 2012 (UTC)
Hello! I wonder how the feature "hlist" works. If I'm not wrong, "hlist" converts lists like this
* List1 * List2 * List3
into
List1 • List2 • List3
My question is: how does that work? Thanks!-- Weltforce ( talk) 19:31, 16 June 2012 (UTC)
This is a minor style issue but many (well ok I know of three!) editors like to place a blank line between the footer templates and the text above it. Is it feasible to add a bit of code into the template that gives the option of placing a half or full line space above the template? It will give a slight improvement in readability. Mobile devices will have to be treated separately. There has been at least one silly debate and edit war about it. See Talk:Reach for the Sky. If is is technically feasible I will bring it up as a WP:MOS discussion. -- Alan Liefting ( talk - contribs) 23:05, 16 June 2012 (UTC)
I'm having difficulty getting a box to be collapsed by default. Is it enough to write "state=collapsed", or is something more needed? SlimVirgin (talk) 21:53, 17 June 2012 (UTC)
I am ready to add a 21st list, or frankly go up to 30. {{ MARepresentatives}} could really use it. A very simple addition to the code which would have no harm. Please advise.— GoldRingChip 12:48, 29 June 2012 (UTC)
a • b • c
becomes
* a * b * c
but the output still looks the same. Makes it easier to edit lists, especially if you want to sort them. -- WOSlinker ( talk) 14:28, 29 June 2012 (UTC)
For templates like {{
MNAC}}, whose title is not in English, it would be useful to have a |title_lang=
, to take a two-letter ISO code for the relevant language, with output comparable to |native_name_lang=
in {{
Infobox person}}.
Andy Mabbett (Pigsonthewing);
Talk to Andy;
Andy's edits
19:31, 17 July 2012 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Two things here: First, Tidy isn't required if someone wants to import this template to another wiki; I have successfully imported and used {{
Navbox}}
on several wikis without Tidy, without having to modify the template at all, so the notices stating that Tidy is required should probably be removed (this does not require an admin, and is therefore not part of the edit request; I'm just looking for consensus or caveats that I'm unaware of).
Second (and, I suppose, actually a counterpoint to my first comment =D ), if Navbox is used together with the hlist class on wikis without Tidy, it has some caveats that must be worked around (
bugzilla:39066). While I still haven't figured out the wrapping bug (would anyone more familiar with the CSS for Navbox and hlists like to have a crack at that one?), the broken HTML can be fixed by closing tags on the line following the {{{listN}}}
markup instead of on the same line, as seen
here. This change doesn't have any adverse side effects as far as I can tell, so could it be done here on Wikipedia as well, so other reusers won't have to worry about this? 「
ディノ奴
千?!」
? ·
☎ Dinoguy1000
21:45, 6 August 2012 (UTC)
Spacing things in this template can cause unnecessary paragraph tags to show up, so that would be something to double check. The other thing that could be a problem is all of this in context of the family of navbox templates (with columns, subgroup, etc.).
On Tidy, that can be edited via template:navbox/doc per the usual editing process. I've turned off the notice until those other test cases are checked and there's a consensus. -- Izno ( talk) 23:03, 6 August 2012 (UTC)
{{{above}}}
(and, therefore, probably also {{{below}}}
) causes a paragraph tag to be added, which changes the padding and line-height. I wouldn't be surprised if paragraph tags are also being added to the listN
's, but if so, they're not changing anything visually. They also don't seem to affect child navboxes; the first navbox
here uses child navboxes to display the subheaders and subsequent groups/lists, with no change in padding or spacing (except the previously noted above
. 「
ディノ奴
千?!」
? ·
☎ Dinoguy1000
23:17, 6 August 2012 (UTC)People keep putting release years in brackets following films in navboxes – an example:
This strikes me as being curious and unnecessary. Dates aren't put after albums, books, etc. in navboxes, so why should this be an exception? I think it would be good if we could come to a consensus on this.
On another note, I also think these group classings are unnecessary, given that there are only six films here, and that it would look neater and simpler without them. Lachlan Foley ( talk) 00:34, 16 September 2012 (UTC)
Does anyone know why this template is expanding beyond the width of the page? Thanks. Rangoon11 ( talk) 18:26, 21 September 2012 (UTC)
<!-- Served by mw28 in 0.137 secs. -->
</body>
</html>
Served by
" up to "secs.
", and paste it below. Then I can add the relevant server code to the bug report at
bugzilla:38273. Thanks. --
Redrose64 (
talk)
18:53, 21 September 2012 (UTC)
) is enough to trigger the error. —
Edokter (
talk) —
18:23, 23 September 2012 (UTC)With HTML5 enabled, this template now generates two validation errors due to the use of cellspacing
. See
[2], which is a validation of the sandbox without the doc page (which generates a lot of errors due to other templates). ---—
Gadget850 (Ed)
talk
12:20, 24 September 2012 (UTC)
Sorry if this has been brought up, but I just noticed hlist navboxes have an extra, pointless dot after the final item. Now that I've noticed it, I can't unnotice it. I think it might drive me insane. Even if it doesn't, it looks bad. Is there a good reason for it? If not, it should be fixed. Thanks. InedibleHulk ( talk) 02:22, 25 October 2012 (UTC)
I could ask a long, complicated question about this, but it would be simpler to ask whether what I am trying to do at User:Rrius/Userboxes can work. - Rrius ( talk) 00:35, 15 November 2012 (UTC)
<td style="width: 238px;">(the width specified in the userbox's code), and it didn't work. - Rrius ( talk) 02:36, 15 November 2012 (UTC)
Is there any special way to set the groupstyle? Please see the recent edit history of
Template:Middle-earth films where the group boxes did not accept the intended background colour. I've also experienced this problem last night when playing around with {{
Authority control}} in my user sandbox. It seems that contrary to what the documentation tells us, |groupstyle = background: foo;
doesn't work.
De728631 (
talk)
16:30, 18 November 2012 (UTC)
| groupstyle = {{#if|{{{embed|yes}}|background: white;}}}
but that didn't work, while I could easily set |listclass
that way.
De728631 (
talk)
20:51, 18 November 2012 (UTC)
Mismatching delimiters all over the place. {{#if:{{{embed|yes}}}|background: white;}}. Alternatively, you may be looking for {{#ifeq:{{{embed|yes}}}|yes|background: white;}}. Not sure.
That said, you should really avoid setting colors per WP:COLOR. (I would tend to argue the more extreme position that styling should not be allowed except widths, and even that only at the navbox level.) -- Izno ( talk) 20:58, 18 November 2012 (UTC)
Answers to the above are not explicit on Template:Navbox, although "navbar" appears 6 times in Template:Navbox with the 1st mention saying what a navbar parameter does. "See also" is does not say explicitly what the distinction is between navbar and sidebar either or what the respective links do. IMO they should be worked into a separate an earlier section, not concealed in "See also". Thanks. --
Thomasmeeks (
talk)
03:30, 8 December 2012 (UTC)
I noticed that this template creates 2px height blank rows to create gaps between the rows. this works, in most cases, but I have noticed a quirk, if you compare the following:
if you look, the second version has a spurious 2px gap at the top of the subgroups. of course, the easy solution for this is to simply not use high numbered group/list values without the low numbered ones. however, if you do DePiep will quickly revert your changes. so, it appears the only solution is to change this template. it would be nice to have the padding set using style statements, rather than blank rows, but I understand this is difficult to do with CSS (see, e.g., this thread)? I understand that we want to avoid introducing a bunch of new #if statements like we have for the first couple rows. any ideas? Frietjes ( talk) 17:22, 23 December 2012 (UTC)
evenodd = swap
), but today here you do not mention that and you propose to change the navbox template? -
DePiep (
talk)
19:28, 23 December 2012 (UTC)
group1=... | list1=...
.group1
} going wrong| evenodd = swap
. —
Edokter (
talk) —
18:38, 23 December 2012 (UTC)
oddstyle = background: transparent evenstyle = background: #f7f7f7;
|groupn=
|listn=
and none of these pairs are mandatory; nor is it required to use consecutive numbers (I have constructed navboxes that used rows 1-6 and 11-14, because the groupings fell into two distinct categories). I also fail to see why you would need to mess around with |oddstyle=
|evenstyle=
when we have |evenodd=swap
. --
Redrose64 (
talk)
21:49, 23 December 2012 (UTC)
|oddstyle=
|evenstyle=
- I agree. I just mentioned it to show the option, and I already noted that others had pointed to a better option. Still, it is a correct coding, documented and CSS & template consistent.|groupn=
|listn=
. I cannot help or correct your failing. Edokter has explained and demonstrated, in this thread, that using "group1" or "group2" solves the issue of: BOTH alternating grey/transparent bg AND prevent top padding 2px (gap).group1
or group2
prevents the 2px gap appearing. First group in a (sub)navbox template group3
or higher does introduce the 2px gap. Using n=1 or n=2 also allows steering the even/odd (transparent/grey) bg. All fine. So, acrtually it does matter where the sequence starts (1 and 2 good, 3 and up bad). That is what this thread is about. Other remarks (e.g. about setting a bg color) are illustratative or alternatives, interesting but not needed. -
DePiep (
talk)
23:05, 23 December 2012 (UTC)Please take a look at Wikipedia:Village pump (technical)#Navboxes and touch devices. Thanks, — This, that, and the other (talk) 09:28, 2 January 2013 (UTC)
Can someone help fix {{ Yugoslavia timeline}} so that it actually supports a {{ collapsible option}}? I tried the basic conversion, put all the content in navbox list1, but I get nothing rendered that way. See Template:Yugoslavia timeline/sandbox. -- Joy [shallot] ( talk) 10:28, 6 January 2013 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please replace the following line of the template's code (line 8)
--><table cellspacing="0" class="nowraplinks {{{bodyclass|}}} {{#if:{{{title|}}}|{{#switch:{{{state|}}}|<!--
... with ...
--><table cellspacing="0" class="nowraplinks {{{bodyclass|{{{class|}}}}}} {{#if:{{{title|}}}|{{#switch:{{{state|}}}|<!--
... in order to provide the alterative name class
for the bodyclass
parameter (complementing the style/bodystyle parameter; and as implemented in the Sidebar templates).
CsDix ( talk) 13:44, 13 February 2013 (UTC)
style
is already offered here as an alternative to bodystyle
and class/bodyclass
is already in use in Sidebars. Apologies if the above didn't make that sufficiently clear.
CsDix (
talk)
14:17, 13 February 2013 (UTC)
bodystyle
's alternative name (style
).
CsDix (
talk)
22:37, 13 February 2013 (UTC){{
edit protected}}
template. --
Redrose64 (
talk)
21:30, 13 February 2013 (UTC)![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please replace the line...
--><tr><td class="navbox-abovebelow {{{belowclass|}}}" style="{{{basestyle|}}};{{{belowstyle|}}}" <!--
...near the end of the code (in the "---Below---" section) with...
--><tr><td class="{{#ifeq:{{{belowclass|}}}|navbox-title | |navbox-abovebelow}} {{{belowclass|}}}" style="{{{basestyle|}}};{{{belowstyle|}}}" <!--
...to allow |belowclass=navbox-title
to override the default "navbox-abovebelow" class setting. (I believe – hope – this is simply an omission rather than something that requires consensus harvesting.)
CsDix ( talk) 00:57, 25 February 2013 (UTC)
Using "listclass=hlist hnum", numbered list appears on only list1. Is this an intent function? And if I want to show numbered list for all list2, list3, ..., what should I do? — Preceding unsigned comment added by Nullzero ( talk • contribs) 11:55, 24 February 2013 (UTC)
|
|
|
|