![]() | 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 15 | Archive 16 | Archive 17 | Archive 18 | Archive 19 | Archive 20 | → | Archive 24 |
Example:
why even if i say width: 120px;, its width is still not 120px? C933103 ( talk) 21:18, 2 September 2014 (UTC)
-- [[
User:Edokter]] {{
talk}}
21:27, 2 September 2014 (UTC)
The advice in that box doesn't appear to have been changed much since I originally wrote it some years ago. How much of it is still relevant at this point? (At the very least, it needs rewritten to address the template's current Lua version, and I'm not sure if it still requires Tidy to be installed.) 「 ディノ奴 千?!」 ? · ☎ Dinoguy1000 01:03, 6 September 2014 (UTC)
-- [[
User:Edokter]] {{
talk}}
08:55, 6 September 2014 (UTC)I imported all possibly necessary items for Navbox from enwiki tu Sundanese (suwiki) including common.css, common.js, monobook.css, monobook.js. The problem is : Navbox doesn't appear properly, only navbox border appear, no Navbar, no text, no contents. Example : su:Template:Glaciers of Iceland. What else should we do? Thank you -- Tedi ( talk) 02:25, 16 October 2014 (UTC)
Why the default behavior is "autocollapse"? There are many articles with one template. Then is a problem: the expanded template takes more place on the page, attracts a lot of attention. Is not better "collapsed" as default behavior?-- Unikalinho ( talk) 14:55, 3 November 2014 (UTC)
|state=collapsed
rather than leaving |state=autocollapse
) made over the past
24 hours, as he was making a unilateral decision to appease his own personal aesthetic rather than seeking consensus or even leaving a reason for his edits. This editor has also done this same thing across several projects other than
WP:FOOTY. --
Jkudlick (
talk) 17:49, 3 November 2014 (UTC)autocollapse
was reached years ago before you or I began editing. If you wish to change the display of the navbox on that many articles, start a discussion on the project talk page rather than enforcing your personal aesthetic. --
Jkudlick (
talk) 18:03, 3 November 2014 (UTC)autocollapse
was reached years ago before you or I began editing" — can I see this consensus?--
Unikalinho (
talk) 18:09, 3 November 2014 (UTC)
Any objections to switching to mw.html? Module:Navbox/sandbox has, what should be, a working version using mw.html. Frietjes ( talk) 17:57, 18 October 2014 (UTC)
-- [[
User:Edokter]] {{
talk}}
21:36, 18 October 2014 (UTC)
.attr('cellspacing', 0)
is obsolete. I think this should be .css('border-spacing', '0px')
. Looks like there are two instances of this. --
Gadget850
talk 14:59, 14 November 2014 (UTC)
-- [[
User:Edokter]] {{
talk}}
15:40, 14 November 2014 (UTC)
-- [[
User:Edokter]] {{
talk}}
19:02, 14 November 2014 (UTC)
-- [[
User:Edokter]] {{
talk}}
20:29, 14 November 2014 (UTC)@
Jackmcbarn,
Dinoguy1000,
Edokter,
WOSlinker, and
Isaacl: it would be helpful to avoid
adding nowrap manually to lists. this is possible by preprocessing the input and adding the appropriate span tags. as a proof-of-concept, see
Module:Navbox with nowrap lists. is there any objection to adding this feature to
Module:navbox? in particular, it would not happen unless someone uses |nowraplists=yes
or some similar parameter or class. I really don't care how it is triggered, but it would be very helpful to not have to explicitly add nowrap to each list item in these cases. if you want to see it in action, try
template:navbox/sandbox3. (notifying recent editors of the module and the author of
Module:Team roster navbox)
Frietjes (
talk) 19:44, 8 December 2014 (UTC)
-- [[
User:Edokter]] {{
talk}}
20:25, 8 December 2014 (UTC)-- [[
User:Edokter]] {{
talk}}
20:25, 8 December 2014 (UTC)
|nowraplists=yes
, we are ready to go. I wasn't sure if this was the best parameter name (but seems fine to me).
Frietjes (
talk) 21:21, 9 December 2014 (UTC)
|nowraplistitems=
, or if that is too long, |nowrapitems=
. -- [[
User:Edokter]] {{
talk}}
21:43, 9 December 2014 (UTC)Maybe it would be worth to add check, if the |name=
is suitable? I mean, some people won't know, that you need to fill "name" parameter with the PAGENAME value, otherwise the link will be red. --
Edgars2007 (
talk/
contribs) 16:24, 26 January 2015 (UTC)
|name=
parameters aren't used unless the name to be displayed is somehow different than the {{
PAGENAME}}. This template is coded in Lua, so that will need to be fixed by someone who knows how to set the default name to the pagename in Lua. — {{U|
Technical 13}} (
e •
t •
c)
16:38, 26 January 2015 (UTC)|name=
parameter is necessary to make the v-t-e links appear at upper left. These links are present more often than absent, so "aren't used unless the name to be displayed is somehow different than the {{
PAGENAME}}" simply isn't true.|name=
set incorrectly are picked up by monthly report
Wikipedia:Database reports/Invalid Navbar links (see
Wikipedia:Bot requests/Archive 62#Navbox templates with wrong names), which I
normally act on within 24 hours, so any redlinks persist for no more than 32 days. --
Redrose64 (
talk) 17:05, 26 January 2015 (UTC)
Here's a tip to avoid wide group cells, which happen due to CSS nowrap: use parameter "groupstyle = white-space: normal;". As far as I can see there is no unfortunately simpler way to do that. Perhaps this trick should be documented. -- Chealer ( talk) 00:01, 30 January 2015 (UTC)
Is there a way to suppress just the "V • T • E" without the "[show]/[hide]" button?--- ARTEST4ECHO( Talk) 22:59, 4 February 2015 (UTC)
|navbar=
parameter, and the show/hide link with the |state=
parameter. They are documented on the template page. -- [[
User:Edokter]] {{
talk}}
23:09, 4 February 2015 (UTC)
|navbar=
parameter. I found the |state=
parameter, but the off and plain hide both. Thanks---
ARTEST4ECHO(
Talk) 20:52, 6 February 2015 (UTC)
-- [[
User:Edokter]] {{
talk}}
21:01, 6 February 2015 (UTC)This template is not visible in the Android App, while the Dutch version is visible. In English I only came across Template:Jesuit, that works fine, but always in collapsed state. Is there a reason for this difference? Wiki-uk ( talk) 21:41, 17 February 2015 (UTC)
I created a proof-of-concept in
Template:Navbox with striping, but this would be more elegant if there were another option for |evenodd=
to enable this feature, rather than the hack that I am using. any comments?
Frietjes (
talk) 18:32, 21 February 2015 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please add the "metadata" class to the whole navbox. Otherwise the multimedia viewer galleries are filled by unrelated icons contained in navboxes. See mw:Help:Extension:Media_Viewer#How_can_I_disable_Media_Viewer_for_unrelated_images.3F for more info. -- Nemo 12:15, 12 November 2014 (UTC)
-- [[
User:Edokter]] {{
talk}}
12:27, 12 November 2014 (UTC)@ Nemo:, are there any particular navboxes that have icons visible in media viewer? Might be possible to modify some other templates, such as {{ Icon}} instead. -- WOSlinker ( talk) 13:09, 14 November 2014 (UTC)
Can someone share some insight wether it is possible to make the navbar links "translatable"? I have a user that keeps reverting
mw:Template:Navbox to the old template code because he doesn't know how to localize the links in
mw:Module:Navbar. I don't know either... but I do know the old template does not provide any translations. -- [[
User:Edokter]] {{
talk}}
16:48, 6 April 2015 (UTC)
Is there any reason {{Navbox}} hasn't been switched to use mw-collapsible
yet? I don't see any discussion anywhere in the archives. 「
ディノ奴
千?!」
? ·
☎ Dinoguy1000 19:34, 21 March 2015 (UTC)
-- [[
User:Edokter]] {{
talk}}
08:14, 22 March 2015 (UTC)-- [[
User:Edokter]] {{
talk}}
09:24, 30 March 2015 (UTC)-- [[
User:Edokter]] {{
talk}}
09:29, 30 March 2015 (UTC)mw-collapsible
; is there a bug for that? Or is that perhaps the default behavior, and I didn't glean that fact from reading the code, and my change therefore overrides that default for all navboxes now? 「
ディノ奴
千?!」
? ·
☎ Dinoguy1000 10:27, 30 March 2015 (UTC)-- [[
User:Edokter]] {{
talk}}
15:31, 30 March 2015 (UTC)jquery.makeCollapsible
, it looks like we should be able to build our own "show"/"hide" link (see for example
lines 324–331, and see
buildDefaultToggleLink()
for how the link itself is built; reading the comment on
lines 225–228 suggests we'd need a mw-customcollapsible-XXX
ID on the navbox, and a mw-customtoggle-XXX
class on the toggle we built (where "XXX" in both cases is some custom string, presumably to help prevent collisions)), which would allow us to apply any custom text color in the header to the link. Unfortunately, my Lua skills aren't up to the challenge in this case - I have no doubt I could come up with something that "works" by faffing about for a couple of hours, but couldn't guarantee it would work well or fit with the style of the rest of the code.autocollapse
issue is one I mentioned twice before, both in my opening comment(s) and in my comment following my edit to the live module. jquery.makeCollapsible
has no handling for an autocollapse mode; see
lines 174–179 for the default case for example. 「
ディノ奴
千?!」
? ·
☎ Dinoguy1000 18:47, 30 March 2015 (UTC)
-- [[
User:Edokter]] {{
talk}}
20:55, 30 March 2015 (UTC).navbox-title .mw-collapsible-toggle a {color: inherit;}
to the relevant stylesheet? As for the autocollapse issue, is it really that hard to replicate locally? For example, if ( $( '.navbox' ).length > 3 ) { $( '.navbox mw-collapsible-toggle' ).click(); }
Mdowdell (
talk) — Preceding
undated comment added 22:58, 30 March 2015 (UTC)
-- [[
User:Edokter]] {{
talk}}
07:29, 31 March 2015 (UTC)-- [[
User:Edokter]] {{
talk}}
16:44, 6 April 2015 (UTC)mw-collapsed
in addition to mw-collapsible
. --
Krinkle (
talk) 01:13, 14 April 2015 (UTC)What is the maximum number of groups or lists in a navbox? Is it finite (limited), or unlimited? GeoffreyT2000 ( talk) 01:12, 16 May 2015 (UTC)
I found a bug in Chrome, see {{
United States Military Academy superintendents}}. The width: 100%;
for the list cell has the opposite effect in Chrome. -- [[
User:Edokter]] {{
talk}}
17:59, 13 June 2015 (UTC)
<a>...</a>
element, which itself is enclosed in a <div>...</div>
element with no attributes - but that div is apparently 316px × 105px. The problem lies with whatever sets that to 316px instead of 120px, the actual image width. --
Redrose64 (
talk) 10:50, 14 June 2015 (UTC)
width: 100%;
in my inspector (set on the <td>
), the dimensions normalize, but not when I disable the width: 0%;
in the image cell. -- [[
User:Edokter]] {{
talk}}
11:54, 14 June 2015 (UTC)
|liststyle=width: auto;
|imagestyle=width: 120px;
(add padding-left and padding-right to taste)|list2=some content
seemed to change the behaviour to give a minimum width image cell (that's why you can't see this behaviour on the testcases subpage). It's possible that this is really more of a doc bug, and the fix would be just to strongly suggest setting the width (and any desired padding) for the image cell in the docs. I've not done any multi-browser testing of those ideas, just some experimentation out of passing curiosity, having been doing a bit of work with Navbox on another wiki.I think there should be a consensus gathered on whether navboxes should allow unlinked information inside a navbox – for example: Template:Jebediah.
I personally think it should not be allowed, and that the whole purpose of a navbox in the first place is to navigate between existing articles, not to fully document, in this case, an artist's discography (that is what a Discography section or article is for). Lachlan Foley ( talk) 04:48, 13 July 2015 (UTC)
It definitely doesn't work as indicated in the documentation, or any other way I can find. Adam Cuerden ( talk) 21:07, 19 July 2015 (UTC)
-- [[
User:Edokter]] {{
talk}}
21:59, 19 July 2015 (UTC)
|list1=
has to be non-empty. --
WOSlinker (
talk) 22:24, 19 July 2015 (UTC)
Hello,
Navbox template is rendering in a rather un-pretty manner as shown in the screenshot below. We have tried several things but no dice. Can someone please take a look and see what we may be missing?
Thank you for your help.
अभय नातू ( talk) 16:46, 2 August 2015 (UTC)
-- [[
User:Edokter]] {{
talk}}
16:56, 2 August 2015 (UTC)
Thank you very much for the quick responses. Made the suggested changes at mw:Snippets/Horizontal lists but no luck yet. I'll try to gather more details/symptoms before asking for more help. I did want to acknowledge your prompt turnaround!
अभय नातू ( talk) 00:57, 3 August 2015 (UTC)
p.s. I should clarify that the rendering is better now (horizontal list instead of vertical) but is on a separate line, not on the same as title line. Probably need more css tweaks. Do let me know if there're classes/scripts I should inspect/tweak first. — Preceding unsigned comment added by अभय नातू ( talk • contribs) 01:00, 3 August 2015 (UTC)
It seems as though the Navbox has been broken somehow on certain categories of pages. From the template page for the Navbox, the good example - University of Michigan page no longer displays the Navbox appearing even though the correct tags are still in the pages' code. This seems to an issue with places and colleges. Can someone help with this? Blanksamurai ( talk) 13:10, 7 August 2015 (UTC)
Hi Izno, I apologize it's an error related to use of Internet Explorer 9 (probably unsupported now). Thanks for following up. Blanksamurai ( talk) 17:30, 7 August 2015 (UTC)
This has been a long time coming. The suggested default for |state=
has been | state = {{{state|}}}
in the doc for some time now. But when navboxes use that extra pipe, the default autocollapse doesn't actually kick in (solitary navboxes do not auto-expand). The trick is removing that extra pipe. The param still allows state changes to be specified when calling the template, but it actually does autocollapse on its own. I've corrected the documentation to reflect this. –
czar 21:57, 7 August 2015 (UTC)
|state=
, literally "{{{state}}}" replaces the collapsed
class; essentially, this is no different than defaulting to expanded
.
Alakzi (
talk) 22:11, 7 August 2015 (UTC)
Some navboxes e.g. Barack Obama account for over 40% of the markup required to render an article. The table based layout also doesn't work on mobile.
I wonder if using JavaScript and JSON stored blobs/wikidata we could reduce the HTML for these templates and make the experience more interactive. Worth exploring? Cc @thedj @gwicke Jdlrobson ( talk) 02:26, 28 July 2015 (UTC) Jdlrobson ( talk) 02:26, 28 July 2015 (UTC)
display:none;
for one of the classes that is associated with every navbox. --
Redrose64 (
talk) 08:07, 28 July 2015 (UTC)
In the case of {{
UK Labour Party}}, is there any reason why | basestyle = background:{{Labour Party (UK)/meta/color}}; color:white;
doesn't apply to the main header's link color as well? The show/hide links and non-linked titles change color with the color:white input, but not the main header. –
czar 00:45, 26 August 2015 (UTC)
color
is not inherited by links. Inside
Module:Navbox, the basestyle
is passed on to
Module:Navbar and is applied to its links directly.
Alakzi (
talk) 07:56, 26 August 2015 (UTC)
-- [[
User:Edokter]] {{
talk}}
16:45, 26 August 2015 (UTC)I've just reverted the change that was made to the navbox module.
It had more than just some colour tracking additions. It included changes to the collapsible code which didn't work in all situations.
Also, noticed on {{ UK Labour Party}} that there was a LUA error: "Lua error in Module:Navbox at line 279: attempt to index local 'key' (a number value)." -- WOSlinker ( talk) 11:35, 7 September 2015 (UTC)
<nowiki>...</nowiki>
tag in {{
Labour Party (UK)/meta/color}} is retained; <nowiki>#DC241f</nowiki>
is an invalid colour.
Alakzi (
talk) 13:02, 7 September 2015 (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 15 | Archive 16 | Archive 17 | Archive 18 | Archive 19 | Archive 20 | → | Archive 24 |
Example:
why even if i say width: 120px;, its width is still not 120px? C933103 ( talk) 21:18, 2 September 2014 (UTC)
-- [[
User:Edokter]] {{
talk}}
21:27, 2 September 2014 (UTC)
The advice in that box doesn't appear to have been changed much since I originally wrote it some years ago. How much of it is still relevant at this point? (At the very least, it needs rewritten to address the template's current Lua version, and I'm not sure if it still requires Tidy to be installed.) 「 ディノ奴 千?!」 ? · ☎ Dinoguy1000 01:03, 6 September 2014 (UTC)
-- [[
User:Edokter]] {{
talk}}
08:55, 6 September 2014 (UTC)I imported all possibly necessary items for Navbox from enwiki tu Sundanese (suwiki) including common.css, common.js, monobook.css, monobook.js. The problem is : Navbox doesn't appear properly, only navbox border appear, no Navbar, no text, no contents. Example : su:Template:Glaciers of Iceland. What else should we do? Thank you -- Tedi ( talk) 02:25, 16 October 2014 (UTC)
Why the default behavior is "autocollapse"? There are many articles with one template. Then is a problem: the expanded template takes more place on the page, attracts a lot of attention. Is not better "collapsed" as default behavior?-- Unikalinho ( talk) 14:55, 3 November 2014 (UTC)
|state=collapsed
rather than leaving |state=autocollapse
) made over the past
24 hours, as he was making a unilateral decision to appease his own personal aesthetic rather than seeking consensus or even leaving a reason for his edits. This editor has also done this same thing across several projects other than
WP:FOOTY. --
Jkudlick (
talk) 17:49, 3 November 2014 (UTC)autocollapse
was reached years ago before you or I began editing. If you wish to change the display of the navbox on that many articles, start a discussion on the project talk page rather than enforcing your personal aesthetic. --
Jkudlick (
talk) 18:03, 3 November 2014 (UTC)autocollapse
was reached years ago before you or I began editing" — can I see this consensus?--
Unikalinho (
talk) 18:09, 3 November 2014 (UTC)
Any objections to switching to mw.html? Module:Navbox/sandbox has, what should be, a working version using mw.html. Frietjes ( talk) 17:57, 18 October 2014 (UTC)
-- [[
User:Edokter]] {{
talk}}
21:36, 18 October 2014 (UTC)
.attr('cellspacing', 0)
is obsolete. I think this should be .css('border-spacing', '0px')
. Looks like there are two instances of this. --
Gadget850
talk 14:59, 14 November 2014 (UTC)
-- [[
User:Edokter]] {{
talk}}
15:40, 14 November 2014 (UTC)
-- [[
User:Edokter]] {{
talk}}
19:02, 14 November 2014 (UTC)
-- [[
User:Edokter]] {{
talk}}
20:29, 14 November 2014 (UTC)@
Jackmcbarn,
Dinoguy1000,
Edokter,
WOSlinker, and
Isaacl: it would be helpful to avoid
adding nowrap manually to lists. this is possible by preprocessing the input and adding the appropriate span tags. as a proof-of-concept, see
Module:Navbox with nowrap lists. is there any objection to adding this feature to
Module:navbox? in particular, it would not happen unless someone uses |nowraplists=yes
or some similar parameter or class. I really don't care how it is triggered, but it would be very helpful to not have to explicitly add nowrap to each list item in these cases. if you want to see it in action, try
template:navbox/sandbox3. (notifying recent editors of the module and the author of
Module:Team roster navbox)
Frietjes (
talk) 19:44, 8 December 2014 (UTC)
-- [[
User:Edokter]] {{
talk}}
20:25, 8 December 2014 (UTC)-- [[
User:Edokter]] {{
talk}}
20:25, 8 December 2014 (UTC)
|nowraplists=yes
, we are ready to go. I wasn't sure if this was the best parameter name (but seems fine to me).
Frietjes (
talk) 21:21, 9 December 2014 (UTC)
|nowraplistitems=
, or if that is too long, |nowrapitems=
. -- [[
User:Edokter]] {{
talk}}
21:43, 9 December 2014 (UTC)Maybe it would be worth to add check, if the |name=
is suitable? I mean, some people won't know, that you need to fill "name" parameter with the PAGENAME value, otherwise the link will be red. --
Edgars2007 (
talk/
contribs) 16:24, 26 January 2015 (UTC)
|name=
parameters aren't used unless the name to be displayed is somehow different than the {{
PAGENAME}}. This template is coded in Lua, so that will need to be fixed by someone who knows how to set the default name to the pagename in Lua. — {{U|
Technical 13}} (
e •
t •
c)
16:38, 26 January 2015 (UTC)|name=
parameter is necessary to make the v-t-e links appear at upper left. These links are present more often than absent, so "aren't used unless the name to be displayed is somehow different than the {{
PAGENAME}}" simply isn't true.|name=
set incorrectly are picked up by monthly report
Wikipedia:Database reports/Invalid Navbar links (see
Wikipedia:Bot requests/Archive 62#Navbox templates with wrong names), which I
normally act on within 24 hours, so any redlinks persist for no more than 32 days. --
Redrose64 (
talk) 17:05, 26 January 2015 (UTC)
Here's a tip to avoid wide group cells, which happen due to CSS nowrap: use parameter "groupstyle = white-space: normal;". As far as I can see there is no unfortunately simpler way to do that. Perhaps this trick should be documented. -- Chealer ( talk) 00:01, 30 January 2015 (UTC)
Is there a way to suppress just the "V • T • E" without the "[show]/[hide]" button?--- ARTEST4ECHO( Talk) 22:59, 4 February 2015 (UTC)
|navbar=
parameter, and the show/hide link with the |state=
parameter. They are documented on the template page. -- [[
User:Edokter]] {{
talk}}
23:09, 4 February 2015 (UTC)
|navbar=
parameter. I found the |state=
parameter, but the off and plain hide both. Thanks---
ARTEST4ECHO(
Talk) 20:52, 6 February 2015 (UTC)
-- [[
User:Edokter]] {{
talk}}
21:01, 6 February 2015 (UTC)This template is not visible in the Android App, while the Dutch version is visible. In English I only came across Template:Jesuit, that works fine, but always in collapsed state. Is there a reason for this difference? Wiki-uk ( talk) 21:41, 17 February 2015 (UTC)
I created a proof-of-concept in
Template:Navbox with striping, but this would be more elegant if there were another option for |evenodd=
to enable this feature, rather than the hack that I am using. any comments?
Frietjes (
talk) 18:32, 21 February 2015 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please add the "metadata" class to the whole navbox. Otherwise the multimedia viewer galleries are filled by unrelated icons contained in navboxes. See mw:Help:Extension:Media_Viewer#How_can_I_disable_Media_Viewer_for_unrelated_images.3F for more info. -- Nemo 12:15, 12 November 2014 (UTC)
-- [[
User:Edokter]] {{
talk}}
12:27, 12 November 2014 (UTC)@ Nemo:, are there any particular navboxes that have icons visible in media viewer? Might be possible to modify some other templates, such as {{ Icon}} instead. -- WOSlinker ( talk) 13:09, 14 November 2014 (UTC)
Can someone share some insight wether it is possible to make the navbar links "translatable"? I have a user that keeps reverting
mw:Template:Navbox to the old template code because he doesn't know how to localize the links in
mw:Module:Navbar. I don't know either... but I do know the old template does not provide any translations. -- [[
User:Edokter]] {{
talk}}
16:48, 6 April 2015 (UTC)
Is there any reason {{Navbox}} hasn't been switched to use mw-collapsible
yet? I don't see any discussion anywhere in the archives. 「
ディノ奴
千?!」
? ·
☎ Dinoguy1000 19:34, 21 March 2015 (UTC)
-- [[
User:Edokter]] {{
talk}}
08:14, 22 March 2015 (UTC)-- [[
User:Edokter]] {{
talk}}
09:24, 30 March 2015 (UTC)-- [[
User:Edokter]] {{
talk}}
09:29, 30 March 2015 (UTC)mw-collapsible
; is there a bug for that? Or is that perhaps the default behavior, and I didn't glean that fact from reading the code, and my change therefore overrides that default for all navboxes now? 「
ディノ奴
千?!」
? ·
☎ Dinoguy1000 10:27, 30 March 2015 (UTC)-- [[
User:Edokter]] {{
talk}}
15:31, 30 March 2015 (UTC)jquery.makeCollapsible
, it looks like we should be able to build our own "show"/"hide" link (see for example
lines 324–331, and see
buildDefaultToggleLink()
for how the link itself is built; reading the comment on
lines 225–228 suggests we'd need a mw-customcollapsible-XXX
ID on the navbox, and a mw-customtoggle-XXX
class on the toggle we built (where "XXX" in both cases is some custom string, presumably to help prevent collisions)), which would allow us to apply any custom text color in the header to the link. Unfortunately, my Lua skills aren't up to the challenge in this case - I have no doubt I could come up with something that "works" by faffing about for a couple of hours, but couldn't guarantee it would work well or fit with the style of the rest of the code.autocollapse
issue is one I mentioned twice before, both in my opening comment(s) and in my comment following my edit to the live module. jquery.makeCollapsible
has no handling for an autocollapse mode; see
lines 174–179 for the default case for example. 「
ディノ奴
千?!」
? ·
☎ Dinoguy1000 18:47, 30 March 2015 (UTC)
-- [[
User:Edokter]] {{
talk}}
20:55, 30 March 2015 (UTC).navbox-title .mw-collapsible-toggle a {color: inherit;}
to the relevant stylesheet? As for the autocollapse issue, is it really that hard to replicate locally? For example, if ( $( '.navbox' ).length > 3 ) { $( '.navbox mw-collapsible-toggle' ).click(); }
Mdowdell (
talk) — Preceding
undated comment added 22:58, 30 March 2015 (UTC)
-- [[
User:Edokter]] {{
talk}}
07:29, 31 March 2015 (UTC)-- [[
User:Edokter]] {{
talk}}
16:44, 6 April 2015 (UTC)mw-collapsed
in addition to mw-collapsible
. --
Krinkle (
talk) 01:13, 14 April 2015 (UTC)What is the maximum number of groups or lists in a navbox? Is it finite (limited), or unlimited? GeoffreyT2000 ( talk) 01:12, 16 May 2015 (UTC)
I found a bug in Chrome, see {{
United States Military Academy superintendents}}. The width: 100%;
for the list cell has the opposite effect in Chrome. -- [[
User:Edokter]] {{
talk}}
17:59, 13 June 2015 (UTC)
<a>...</a>
element, which itself is enclosed in a <div>...</div>
element with no attributes - but that div is apparently 316px × 105px. The problem lies with whatever sets that to 316px instead of 120px, the actual image width. --
Redrose64 (
talk) 10:50, 14 June 2015 (UTC)
width: 100%;
in my inspector (set on the <td>
), the dimensions normalize, but not when I disable the width: 0%;
in the image cell. -- [[
User:Edokter]] {{
talk}}
11:54, 14 June 2015 (UTC)
|liststyle=width: auto;
|imagestyle=width: 120px;
(add padding-left and padding-right to taste)|list2=some content
seemed to change the behaviour to give a minimum width image cell (that's why you can't see this behaviour on the testcases subpage). It's possible that this is really more of a doc bug, and the fix would be just to strongly suggest setting the width (and any desired padding) for the image cell in the docs. I've not done any multi-browser testing of those ideas, just some experimentation out of passing curiosity, having been doing a bit of work with Navbox on another wiki.I think there should be a consensus gathered on whether navboxes should allow unlinked information inside a navbox – for example: Template:Jebediah.
I personally think it should not be allowed, and that the whole purpose of a navbox in the first place is to navigate between existing articles, not to fully document, in this case, an artist's discography (that is what a Discography section or article is for). Lachlan Foley ( talk) 04:48, 13 July 2015 (UTC)
It definitely doesn't work as indicated in the documentation, or any other way I can find. Adam Cuerden ( talk) 21:07, 19 July 2015 (UTC)
-- [[
User:Edokter]] {{
talk}}
21:59, 19 July 2015 (UTC)
|list1=
has to be non-empty. --
WOSlinker (
talk) 22:24, 19 July 2015 (UTC)
Hello,
Navbox template is rendering in a rather un-pretty manner as shown in the screenshot below. We have tried several things but no dice. Can someone please take a look and see what we may be missing?
Thank you for your help.
अभय नातू ( talk) 16:46, 2 August 2015 (UTC)
-- [[
User:Edokter]] {{
talk}}
16:56, 2 August 2015 (UTC)
Thank you very much for the quick responses. Made the suggested changes at mw:Snippets/Horizontal lists but no luck yet. I'll try to gather more details/symptoms before asking for more help. I did want to acknowledge your prompt turnaround!
अभय नातू ( talk) 00:57, 3 August 2015 (UTC)
p.s. I should clarify that the rendering is better now (horizontal list instead of vertical) but is on a separate line, not on the same as title line. Probably need more css tweaks. Do let me know if there're classes/scripts I should inspect/tweak first. — Preceding unsigned comment added by अभय नातू ( talk • contribs) 01:00, 3 August 2015 (UTC)
It seems as though the Navbox has been broken somehow on certain categories of pages. From the template page for the Navbox, the good example - University of Michigan page no longer displays the Navbox appearing even though the correct tags are still in the pages' code. This seems to an issue with places and colleges. Can someone help with this? Blanksamurai ( talk) 13:10, 7 August 2015 (UTC)
Hi Izno, I apologize it's an error related to use of Internet Explorer 9 (probably unsupported now). Thanks for following up. Blanksamurai ( talk) 17:30, 7 August 2015 (UTC)
This has been a long time coming. The suggested default for |state=
has been | state = {{{state|}}}
in the doc for some time now. But when navboxes use that extra pipe, the default autocollapse doesn't actually kick in (solitary navboxes do not auto-expand). The trick is removing that extra pipe. The param still allows state changes to be specified when calling the template, but it actually does autocollapse on its own. I've corrected the documentation to reflect this. –
czar 21:57, 7 August 2015 (UTC)
|state=
, literally "{{{state}}}" replaces the collapsed
class; essentially, this is no different than defaulting to expanded
.
Alakzi (
talk) 22:11, 7 August 2015 (UTC)
Some navboxes e.g. Barack Obama account for over 40% of the markup required to render an article. The table based layout also doesn't work on mobile.
I wonder if using JavaScript and JSON stored blobs/wikidata we could reduce the HTML for these templates and make the experience more interactive. Worth exploring? Cc @thedj @gwicke Jdlrobson ( talk) 02:26, 28 July 2015 (UTC) Jdlrobson ( talk) 02:26, 28 July 2015 (UTC)
display:none;
for one of the classes that is associated with every navbox. --
Redrose64 (
talk) 08:07, 28 July 2015 (UTC)
In the case of {{
UK Labour Party}}, is there any reason why | basestyle = background:{{Labour Party (UK)/meta/color}}; color:white;
doesn't apply to the main header's link color as well? The show/hide links and non-linked titles change color with the color:white input, but not the main header. –
czar 00:45, 26 August 2015 (UTC)
color
is not inherited by links. Inside
Module:Navbox, the basestyle
is passed on to
Module:Navbar and is applied to its links directly.
Alakzi (
talk) 07:56, 26 August 2015 (UTC)
-- [[
User:Edokter]] {{
talk}}
16:45, 26 August 2015 (UTC)I've just reverted the change that was made to the navbox module.
It had more than just some colour tracking additions. It included changes to the collapsible code which didn't work in all situations.
Also, noticed on {{ UK Labour Party}} that there was a LUA error: "Lua error in Module:Navbox at line 279: attempt to index local 'key' (a number value)." -- WOSlinker ( talk) 11:35, 7 September 2015 (UTC)
<nowiki>...</nowiki>
tag in {{
Labour Party (UK)/meta/color}} is retained; <nowiki>#DC241f</nowiki>
is an invalid colour.
Alakzi (
talk) 13:02, 7 September 2015 (UTC)