![]() | 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 19 | Archive 20 | Archive 21 | Archive 22 | Archive 23 | Archive 24 |
Per the discussions at #Row colour above, I propose updating the module from the sandbox.
For testing, I compared the output from {{ navbox}} and {{ navbox/sandbox}} for several cases—all good. Some other tests follow.
listn
which might not be list1
. That seems more natural to me—if no image is wanted, it should not be included in the navbox.|list1 = {{Navbox/sandbox|subgroup
did not stripe the subgroup navbox and the page was in Category:Navbox orphans. Fixing the subgroup to be the following made the striping work and removed the category:
|list1 = {{Navbox/sandbox|subgroup|orphan=yes
An orphan navbox is a subgroup (child) navbox which is not contained in a normal navbox—that is, the child navbox does not have the correct parent. The category will need monitoring to detect any problems. Adding orphan=yes
makes the child navbox work like a normal navbox as far as striping is concerned, and removes the category.
@ Jc86035 + Izno + Frietjes + anyone: Any thoughts? Johnuniq ( talk) 04:40, 10 March 2017 (UTC)
Anyone wanting to examine the output from a navbox may like to try displaying the formatted html. Johnuniq ( talk) 09:21, 10 March 2017 (UTC)
I updated Module:Navbox. Revert if any problems seen, but also please record what the problems are and where they occur. Johnuniq ( talk) 23:53, 12 March 2017 (UTC)
Some interesting problems are reported in Category:Navbox orphans:
{{Navbox with columns|child|...}}
.The good news is that the articles do not show any problems. Previewing the article with the old module gives an identical display on my system. Johnuniq ( talk) 01:05, 13 March 2017 (UTC)
Following the recent change (above), several templates are, or will be, in Category:Navbox orphans and that puts around 140 articles in the category. There will be more as the job queue catches up. Templates with the problem are in the API list.
I need help to fix these since I'm just a Lua person!
Johnuniq ( talk) 03:52, 15 March 2017 (UTC)
For example, if I go to Carbon_monoxide#Lasers, and click "show", it scrolls me up to the top of the page and the navbox is never open at all. What is wrong? Llightex ( talk) 13:14, 16 May 2017 (UTC)
?action=purge
to the end of the URL). What browser are you using, and do you have any scripts enabled?
Jc86035 (
talk) Use {{
re|Jc86035}}Is it possible to fix cases like
this so that |image=
content is automatically aligned to the right, |imageleft=
content to the left, and main content always centered? --
Obsuser (
talk)
05:35, 19 May 2017 (UTC)
|imagestyle=text-align:right
(|imageleftstyle=text-align:left
) or |right
(|left
) in the [[File:]]
syntax. But is is case with every image i.e. chance that someone added this is smaller than that one didn't (as in my example). Main content is not centered in any case. I played in sandbox with previewing modification of adding the same image on the left if right is defined and left is not (and same image on the right if left is defined and right is not) with visibility:hidden in order to center content but column tags got mixed and it did not work...--
Obsuser (
talk)
09:39, 19 May 2017 (UTC)
|liststyle=padding-left:50px
to offset the 50px width of the image on the right.
Frietjes (
talk)
14:04, 20 May 2017 (UTC)
From the MfD, it is proposed that some features of the above module be merged into Module:Navbox. The proposal is that a new parameter be added. If the parameter is set to yes
, each item in each list would be processed by the module to replace:
item
with:
<span class="nowrap">item</span>
The nowrap span would not be added if it is already present.
Module:Navbox with nowrap lists currently applies that processing to items in each listN
parameter, and to parameters above
and below
(it would also process the seldom-used aboveclass
+ abovestyle
+ belowclass
+ belowstyle
although I assume that is unwanted).
For the parameter name, a December 2014 discussion at Template talk:Navbox/Archive 18#Nowrap lists proposed:
|nowraplists=yes
(from Frietjes; Edokter said that was ambiguous)|nowraplistitems=yes
(from Edokter)|nowrapitems=yes
(shorter alternative from Edokter; supported by Frietjes at MfD)Questions:
nowrapitems
?above
and below
have the nowrap processing?Johnuniq ( talk) 04:47, 23 March 2017 (UTC)
|nowrapitems=
for all items, and |nowraplistitems=
for just the items in the lists parameters, but I think starting with just |nowrapitems=
for all items would be a great start.
Frietjes (
talk)
13:19, 23 March 2017 (UTC)and, the entire process has been torpedoed again, with the added bonus of having functionality removed this time (module was deleted with no solution added). I still don't understand why we can't just add something to this module as suggested above. Frietjes ( talk) 14:40, 1 May 2017 (UTC)
class="nowraplinks..."
is in the output of a navbox (see
my sandbox2 or
permalink). Very briefly and only if you happen to know, what is that about and what would be the effect of nowrapitems=yes at say
Atlanta Braves#Current roster? Is that article the kind of thing aimed at? If not, what is? I would feel more comfortable if I knew what the module changes should achieve in a sandbox test, so if you have an example demonstrating the issue, you might like to edit my sandbox2 to replace its contents.
Johnuniq (
talk)
04:23, 2 May 2017 (UTC)
I updated the sandbox module to handle nowrapitems=yes. I will examine the code in the next day or two because it was rather rushed and is untested. Please use {{ navbox/sandbox}} to try it out. It would be good if a few simple tests could be put somewhere, possibly my sandbox2. Johnuniq ( talk) 11:50, 2 May 2017 (UTC)
{{Navbox | listclass = hlist | nowrapitems = yes | list1 =* {{MOSMETRO-bull|11|text=2}} }}. Johnuniq, any ideas on what is going wrong with this one? otherwise, it looks like it's working great! Frietjes ( talk) 20:01, 4 May 2017 (UTC)
@
Frietjes:
Special:ExpandTemplates gives the following result for {{
MOSMETRO-bull|11|text=2}}
:
[[Third Interchange Contour|<span title=" #11 Third Interchange Contour"><span style="font-weight:bold"><span style="font-family:sans-serif;font-size:15px;color: #fff;background-color: #000000;;border-radius:15px;line-height:15px;"><span style="letter-spacing:-1px"> 11 </span></span></span></span>]]<span > [[Third Interchange Contour|Third Interchange Contour]]</span>
The above is four physical lines. The last three lines start with "#" and the module (when nowrapitems=yes
is used) interprets them as forming a numbered list, so the module inserts the nowrap span around the rest of the physical line that follows each "#". I guess that MOSMETRO-bull should be fixed so it does not produce separate lines. Is that reasonably achievable?
Johnuniq (
talk)
22:49, 4 May 2017 (UTC)
{{#if: ... | #00AABB }}
since the parser inserts a newline before the # making it look like an ordered list item.
Frietjes (
talk)
13:50, 5 May 2017 (UTC)Is there a way to stop separator middle dot from detaching from previous item? Sometimes it gets displayed at the very beginnig of the new line. It could be done in a similar way as external link icon is handled in CS1 modules. -- Obsuser ( talk) 15:43, 7 May 2017 (UTC)
nowrapitems=yes
parameter, or is that irrelevant?<tr> <th scope="row" class="navbox-group">Three examples</th> <td class="navbox-list navbox-odd hlist" style="text-align:left;border-left-width:2px;border-left-style:solid;width:100%;padding:0px"> <div style="padding:0em 0.25em"> *Example 1 *Example 2 *Example 3 </div> </td> </tr>
hlist-items-nowrap
class in
ru:MediaWiki:Common.css for nowrap items.
Iniquity (
talk)
19:22, 1 June 2017 (UTC)I'd like to propose using CSS border-spacing for layout rather than HTML gutter rows. I've made the relevant changes at Module:Navbox/sandbox. Template:Navbox/testcases should show no significant differences in modern browsers or IE ≥ 8. Matt Fitzpatrick ( talk) 05:52, 17 May 2017 (UTC)
:first-child
is CSS 2.1, so this should work all the way back to IE 6.
Matt Fitzpatrick (
talk)
12:13, 17 May 2017 (UTC)renderNavBar
we have 'border:none' to stop the V-T-E links from inheriting border styling from the titlestyle / basestyle. if we are going to use box-shadow for the borders in the basestyle or titlestyle, we probably want to add something similar for 'box-shadow', '-moz-box-shadow', '-webkit-box-shadow'? I had to
execute this revert since it was adding box-shadows to the V-T-E links.
Frietjes (
talk)
23:00, 28 June 2017 (UTC)
extractstyle
function in
Module:Team roster navbox, I pull out only the color and background from the style to pass on to the span inside the links. that module could probably be merged with this one at some point. the only thing that it does that the standard navbox module doesn't do is automatically color links.
Frietjes (
talk)
13:35, 29 June 2017 (UTC)Hello, can anybody help me? I want to move arguments from ru:Module:Navbox to a datatable (for example ru:Module:Navbox/data), is it possible? I am using local variables for localization now, but I think it is a bad way. Iniquity ( talk) 23:56, 1 July 2017 (UTC)
Could someone review and add these edits: 5px padding for images and removal of width:auto in Authority control template so that this cell does not get too wide? -- Obsuser ( talk) 17:25, 9 July 2017 (UTC)
How is the hiding of navbox templates on mobile implemented? I thought it was done through
mediawiki:mobile.css, but it looks like that rule was removed
in May 2016. --
Ahecht (
TALK
PAGE)
20:17, 31 July 2017 (UTC)
In the documentation, it states that It is recommended that one use {{Navbox subgroup}}, but the same result can be reached by using {{Navbox}} with border = child or the first unnamed parameter set to child.
. can someone explain why it's recommended to use {{navbox subgroup}}
instead of {{navbox|subgroup}}
? I would think the recommendation would be the reverse since (1) using {{navbox subgroup}}
is less efficient due to the additional wrapper later, and (2) {{navbox subgroup}}
cannot support more than 20 groups/lists. I am guessing that this recommendation (which was added by
CapitalR in
this edit) was true in the past, but is no longer true?
Frietjes (
talk)
21:18, 14 July 2017 (UTC)
0em 0.75em;
. Is {{
Navbox subgroup}} useful? I have not followed the work done on the module recently regarding using css, but presumably any default padding should be set there.
Johnuniq (
talk)
23:24, 14 July 2017 (UTC)
{{navbox subgroup}}
and {{navbox|subgroup}}
. checking the current
MediaWiki:Common.css I see padding: 0.25em 1em
which is close to the 0em 0.75em
value. if we really want to have less padding for groups in subgroups, I believe we can handle that in
MediaWiki:Common.css as well. It would be great if {{navbox subgroup}}
were a very thin frontend that was functionally equivalent to {{navbox|subgroup}}
.
Frietjes (
talk)
23:40, 14 July 2017 (UTC){{navbox| group1 = group1| list1 = {{navbox subgroup | group1 = group1a | list1 = list1a}}}} {{navbox| group1 = group1| list1 = {{navbox|subgroup | group1 = group1a | list1 = list1a}}}}
There are
thousands of templates that link to
Template:Navbox subgroup. Previewing what happens if the subgroup template is not used shows a very minor difference in spacing—if that difference is desirable, it should be in the main template. Any thoughts on how to proceed? The cautious approach would be to edit a couple of navboxes from the "what links here" list to replace
{{navbox subgroup|...}}
with
{{navbox|subgroup|...}}
then see what happens. A faster strategy would be to replace {{
navbox subgroup}} with a redirect to {{
navbox}}.
Johnuniq (
talk)
04:34, 20 July 2017 (UTC)
border=...
parameter if it is given in the module invoke. I'll ponder that later. Ping me if I go AWOL.
Johnuniq (
talk)
23:10, 17 August 2017 (UTC){{#invoke:Navbox|navbox|border=...}}
at
Template:Navbox subgroup/sandbox (
permalink) would have worked. That template is not listed as a "wrapper" so I would have thought the border
parameter in the invoke would be accepted. Can you recall what made you decide it did not work?
Johnuniq (
talk)
11:36, 18 August 2017 (UTC)
border
parameter never made it into the module but I could not work out why. I decided to remove the wrappers stuff, and now it's working. I will return to ponder what's going on another time.Link to current page in a navbox not disabled when it is via a redirect. Example: Wickham Terrace, Brisbane is a redirect to Wickham Terrace. When a navbox link to Wickham Terrace, Brisbane is viewed in Wickham Terrace it is not disabled. Downsize43 ( talk) 01:09, 22 August 2017 (UTC)
In theory, couldn't this be fixed by checking the redirectTarget of each linked page with the mw.title library? But it might not be desirable because it could use up too much of the expensive parser function quota on a page with a lot of navboxes. Toohool ( talk) 02:42, 23 August 2017 (UTC)
Hello I always get an error when using templates that rely on Module:Navbox. I get always this error: Lua-Feeler in Modul:Navbox, Zeile 241: attempt to index local 'listText' (a nil value). How can this bug be fixed? -- Soued031 ( talk) 11:50, 6 September 2017 (UTC)
Is it possible to do the following? If a page directly invokes
Module:Navbox, if the value at name=
does not equal {{BASEPAGENAME}}
, can the invoking template (but not the pages that transclude the template) be placed in a maintenance category?
Steel1943 (
talk)
22:33, 18 September 2017 (UTC)
I would like to have absolutely 100% control over all of the categories on my platform, but I cannot for the life of me prevent Navboxes from being automatically categorized. I have utilized |nocat=true, and while this has worked elsewhere, isn't doing a single thing to help on my created Navbox template. I would greatly appreciate any information on how to suppress these categories(or category handler altogether, if possible.) 2602:304:CF7D:A010:AC12:8F5E:4AC2:39B6 ( talk) 02:16, 26 September 2017 (UTC)
Should there be e.g. |groupnlang=
parameters? Are they necessary? I tried replacing an incorrect use of {{
lang}} (which uses a span tag) in {{
Irish names}} with |groupnstyle=" xml:lang="ga" lang="ga
but it doesn't seem ideal.
Jc86035 (
talk)
14:24, 24 December 2017 (UTC)
<div>...</div>
instead of <span>...</span>
with the lang tagging?
Frietjes (
talk)
14:37, 24 December 2017 (UTC)
|div=yes
?
Jc86035 (
talk)
14:40, 24 December 2017 (UTC)
I discovered that the wikipedia red link color on the standard navbox title color does not obey the WCAG 2.0 standards for text color contrast below 18pt. Not sure what to do about this. I started a discussion about this at WT:WikiProject Accessibility#Wikipedia red link on wikipedia standard navbox title violates WCAG 2.0, feel free to join in. — hike395 ( talk) 07:33, 3 January 2018 (UTC)
after changes to this module, the "old style" css borders no longer work as expected. The fix is to replace them with box-shadow borders like this. does anyone object to adding tracking to find these? I have put some code in the sandbox. Frietjes ( talk) 19:03, 8 January 2018 (UTC)
args = getArgs(frame, {wrappers = {'Template:Navbox|subgroup', 'Template:Navbox'}})
args = getArgs(frame, {wrappers = {'Template:Navbox subgroup', 'Template:Navbox'}})
args = getArgs(frame)
User:Johnuniq/sandbox2
into the "preview page with this module" box and Show preview. The idea of
Module:Arguments is to merge arguments from the invoking template and the parent wikitext, but that is usually unnecessary overhead. Therefore wrappers can be used to specify the templates which do not pass parameters (they merely wrap the module) and which therefore do not need merging. I can't understand the documentation for Module:Arguments so experiment would be needed to determine what would happen if a border parameter was passed in the parent wikitext as well as from the template.
Johnuniq (
talk)
02:30, 10 January 2018 (UTC)
border
from the template. I don't know if I ever tried that out last August, but I put it into
Module:Navbox/sandbox just now. Does that work?border
so my edit checks for that only. It should work!
Johnuniq (
talk)
02:48, 11 January 2018 (UTC)
%1
with item
using gsub. However, your code is good and I am just mentioning my thoughts for completeness. By the way, your script might be doing more than wanted: check
diff which changed "Carson–Newman" to "Carson to Newman". I might look at it more another time. There were quite a few problems when I converted a zillion articles using the system to the syntax preferred by {{
Football manager history}}. I could see the template might be useful in other cases but I was exhausted by then.
Johnuniq (
talk)
06:53, 12 January 2018 (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 19 | Archive 20 | Archive 21 | Archive 22 | Archive 23 | Archive 24 |
Per the discussions at #Row colour above, I propose updating the module from the sandbox.
For testing, I compared the output from {{ navbox}} and {{ navbox/sandbox}} for several cases—all good. Some other tests follow.
listn
which might not be list1
. That seems more natural to me—if no image is wanted, it should not be included in the navbox.|list1 = {{Navbox/sandbox|subgroup
did not stripe the subgroup navbox and the page was in Category:Navbox orphans. Fixing the subgroup to be the following made the striping work and removed the category:
|list1 = {{Navbox/sandbox|subgroup|orphan=yes
An orphan navbox is a subgroup (child) navbox which is not contained in a normal navbox—that is, the child navbox does not have the correct parent. The category will need monitoring to detect any problems. Adding orphan=yes
makes the child navbox work like a normal navbox as far as striping is concerned, and removes the category.
@ Jc86035 + Izno + Frietjes + anyone: Any thoughts? Johnuniq ( talk) 04:40, 10 March 2017 (UTC)
Anyone wanting to examine the output from a navbox may like to try displaying the formatted html. Johnuniq ( talk) 09:21, 10 March 2017 (UTC)
I updated Module:Navbox. Revert if any problems seen, but also please record what the problems are and where they occur. Johnuniq ( talk) 23:53, 12 March 2017 (UTC)
Some interesting problems are reported in Category:Navbox orphans:
{{Navbox with columns|child|...}}
.The good news is that the articles do not show any problems. Previewing the article with the old module gives an identical display on my system. Johnuniq ( talk) 01:05, 13 March 2017 (UTC)
Following the recent change (above), several templates are, or will be, in Category:Navbox orphans and that puts around 140 articles in the category. There will be more as the job queue catches up. Templates with the problem are in the API list.
I need help to fix these since I'm just a Lua person!
Johnuniq ( talk) 03:52, 15 March 2017 (UTC)
For example, if I go to Carbon_monoxide#Lasers, and click "show", it scrolls me up to the top of the page and the navbox is never open at all. What is wrong? Llightex ( talk) 13:14, 16 May 2017 (UTC)
?action=purge
to the end of the URL). What browser are you using, and do you have any scripts enabled?
Jc86035 (
talk) Use {{
re|Jc86035}}Is it possible to fix cases like
this so that |image=
content is automatically aligned to the right, |imageleft=
content to the left, and main content always centered? --
Obsuser (
talk)
05:35, 19 May 2017 (UTC)
|imagestyle=text-align:right
(|imageleftstyle=text-align:left
) or |right
(|left
) in the [[File:]]
syntax. But is is case with every image i.e. chance that someone added this is smaller than that one didn't (as in my example). Main content is not centered in any case. I played in sandbox with previewing modification of adding the same image on the left if right is defined and left is not (and same image on the right if left is defined and right is not) with visibility:hidden in order to center content but column tags got mixed and it did not work...--
Obsuser (
talk)
09:39, 19 May 2017 (UTC)
|liststyle=padding-left:50px
to offset the 50px width of the image on the right.
Frietjes (
talk)
14:04, 20 May 2017 (UTC)
From the MfD, it is proposed that some features of the above module be merged into Module:Navbox. The proposal is that a new parameter be added. If the parameter is set to yes
, each item in each list would be processed by the module to replace:
item
with:
<span class="nowrap">item</span>
The nowrap span would not be added if it is already present.
Module:Navbox with nowrap lists currently applies that processing to items in each listN
parameter, and to parameters above
and below
(it would also process the seldom-used aboveclass
+ abovestyle
+ belowclass
+ belowstyle
although I assume that is unwanted).
For the parameter name, a December 2014 discussion at Template talk:Navbox/Archive 18#Nowrap lists proposed:
|nowraplists=yes
(from Frietjes; Edokter said that was ambiguous)|nowraplistitems=yes
(from Edokter)|nowrapitems=yes
(shorter alternative from Edokter; supported by Frietjes at MfD)Questions:
nowrapitems
?above
and below
have the nowrap processing?Johnuniq ( talk) 04:47, 23 March 2017 (UTC)
|nowrapitems=
for all items, and |nowraplistitems=
for just the items in the lists parameters, but I think starting with just |nowrapitems=
for all items would be a great start.
Frietjes (
talk)
13:19, 23 March 2017 (UTC)and, the entire process has been torpedoed again, with the added bonus of having functionality removed this time (module was deleted with no solution added). I still don't understand why we can't just add something to this module as suggested above. Frietjes ( talk) 14:40, 1 May 2017 (UTC)
class="nowraplinks..."
is in the output of a navbox (see
my sandbox2 or
permalink). Very briefly and only if you happen to know, what is that about and what would be the effect of nowrapitems=yes at say
Atlanta Braves#Current roster? Is that article the kind of thing aimed at? If not, what is? I would feel more comfortable if I knew what the module changes should achieve in a sandbox test, so if you have an example demonstrating the issue, you might like to edit my sandbox2 to replace its contents.
Johnuniq (
talk)
04:23, 2 May 2017 (UTC)
I updated the sandbox module to handle nowrapitems=yes. I will examine the code in the next day or two because it was rather rushed and is untested. Please use {{ navbox/sandbox}} to try it out. It would be good if a few simple tests could be put somewhere, possibly my sandbox2. Johnuniq ( talk) 11:50, 2 May 2017 (UTC)
{{Navbox | listclass = hlist | nowrapitems = yes | list1 =* {{MOSMETRO-bull|11|text=2}} }}. Johnuniq, any ideas on what is going wrong with this one? otherwise, it looks like it's working great! Frietjes ( talk) 20:01, 4 May 2017 (UTC)
@
Frietjes:
Special:ExpandTemplates gives the following result for {{
MOSMETRO-bull|11|text=2}}
:
[[Third Interchange Contour|<span title=" #11 Third Interchange Contour"><span style="font-weight:bold"><span style="font-family:sans-serif;font-size:15px;color: #fff;background-color: #000000;;border-radius:15px;line-height:15px;"><span style="letter-spacing:-1px"> 11 </span></span></span></span>]]<span > [[Third Interchange Contour|Third Interchange Contour]]</span>
The above is four physical lines. The last three lines start with "#" and the module (when nowrapitems=yes
is used) interprets them as forming a numbered list, so the module inserts the nowrap span around the rest of the physical line that follows each "#". I guess that MOSMETRO-bull should be fixed so it does not produce separate lines. Is that reasonably achievable?
Johnuniq (
talk)
22:49, 4 May 2017 (UTC)
{{#if: ... | #00AABB }}
since the parser inserts a newline before the # making it look like an ordered list item.
Frietjes (
talk)
13:50, 5 May 2017 (UTC)Is there a way to stop separator middle dot from detaching from previous item? Sometimes it gets displayed at the very beginnig of the new line. It could be done in a similar way as external link icon is handled in CS1 modules. -- Obsuser ( talk) 15:43, 7 May 2017 (UTC)
nowrapitems=yes
parameter, or is that irrelevant?<tr> <th scope="row" class="navbox-group">Three examples</th> <td class="navbox-list navbox-odd hlist" style="text-align:left;border-left-width:2px;border-left-style:solid;width:100%;padding:0px"> <div style="padding:0em 0.25em"> *Example 1 *Example 2 *Example 3 </div> </td> </tr>
hlist-items-nowrap
class in
ru:MediaWiki:Common.css for nowrap items.
Iniquity (
talk)
19:22, 1 June 2017 (UTC)I'd like to propose using CSS border-spacing for layout rather than HTML gutter rows. I've made the relevant changes at Module:Navbox/sandbox. Template:Navbox/testcases should show no significant differences in modern browsers or IE ≥ 8. Matt Fitzpatrick ( talk) 05:52, 17 May 2017 (UTC)
:first-child
is CSS 2.1, so this should work all the way back to IE 6.
Matt Fitzpatrick (
talk)
12:13, 17 May 2017 (UTC)renderNavBar
we have 'border:none' to stop the V-T-E links from inheriting border styling from the titlestyle / basestyle. if we are going to use box-shadow for the borders in the basestyle or titlestyle, we probably want to add something similar for 'box-shadow', '-moz-box-shadow', '-webkit-box-shadow'? I had to
execute this revert since it was adding box-shadows to the V-T-E links.
Frietjes (
talk)
23:00, 28 June 2017 (UTC)
extractstyle
function in
Module:Team roster navbox, I pull out only the color and background from the style to pass on to the span inside the links. that module could probably be merged with this one at some point. the only thing that it does that the standard navbox module doesn't do is automatically color links.
Frietjes (
talk)
13:35, 29 June 2017 (UTC)Hello, can anybody help me? I want to move arguments from ru:Module:Navbox to a datatable (for example ru:Module:Navbox/data), is it possible? I am using local variables for localization now, but I think it is a bad way. Iniquity ( talk) 23:56, 1 July 2017 (UTC)
Could someone review and add these edits: 5px padding for images and removal of width:auto in Authority control template so that this cell does not get too wide? -- Obsuser ( talk) 17:25, 9 July 2017 (UTC)
How is the hiding of navbox templates on mobile implemented? I thought it was done through
mediawiki:mobile.css, but it looks like that rule was removed
in May 2016. --
Ahecht (
TALK
PAGE)
20:17, 31 July 2017 (UTC)
In the documentation, it states that It is recommended that one use {{Navbox subgroup}}, but the same result can be reached by using {{Navbox}} with border = child or the first unnamed parameter set to child.
. can someone explain why it's recommended to use {{navbox subgroup}}
instead of {{navbox|subgroup}}
? I would think the recommendation would be the reverse since (1) using {{navbox subgroup}}
is less efficient due to the additional wrapper later, and (2) {{navbox subgroup}}
cannot support more than 20 groups/lists. I am guessing that this recommendation (which was added by
CapitalR in
this edit) was true in the past, but is no longer true?
Frietjes (
talk)
21:18, 14 July 2017 (UTC)
0em 0.75em;
. Is {{
Navbox subgroup}} useful? I have not followed the work done on the module recently regarding using css, but presumably any default padding should be set there.
Johnuniq (
talk)
23:24, 14 July 2017 (UTC)
{{navbox subgroup}}
and {{navbox|subgroup}}
. checking the current
MediaWiki:Common.css I see padding: 0.25em 1em
which is close to the 0em 0.75em
value. if we really want to have less padding for groups in subgroups, I believe we can handle that in
MediaWiki:Common.css as well. It would be great if {{navbox subgroup}}
were a very thin frontend that was functionally equivalent to {{navbox|subgroup}}
.
Frietjes (
talk)
23:40, 14 July 2017 (UTC){{navbox| group1 = group1| list1 = {{navbox subgroup | group1 = group1a | list1 = list1a}}}} {{navbox| group1 = group1| list1 = {{navbox|subgroup | group1 = group1a | list1 = list1a}}}}
There are
thousands of templates that link to
Template:Navbox subgroup. Previewing what happens if the subgroup template is not used shows a very minor difference in spacing—if that difference is desirable, it should be in the main template. Any thoughts on how to proceed? The cautious approach would be to edit a couple of navboxes from the "what links here" list to replace
{{navbox subgroup|...}}
with
{{navbox|subgroup|...}}
then see what happens. A faster strategy would be to replace {{
navbox subgroup}} with a redirect to {{
navbox}}.
Johnuniq (
talk)
04:34, 20 July 2017 (UTC)
border=...
parameter if it is given in the module invoke. I'll ponder that later. Ping me if I go AWOL.
Johnuniq (
talk)
23:10, 17 August 2017 (UTC){{#invoke:Navbox|navbox|border=...}}
at
Template:Navbox subgroup/sandbox (
permalink) would have worked. That template is not listed as a "wrapper" so I would have thought the border
parameter in the invoke would be accepted. Can you recall what made you decide it did not work?
Johnuniq (
talk)
11:36, 18 August 2017 (UTC)
border
parameter never made it into the module but I could not work out why. I decided to remove the wrappers stuff, and now it's working. I will return to ponder what's going on another time.Link to current page in a navbox not disabled when it is via a redirect. Example: Wickham Terrace, Brisbane is a redirect to Wickham Terrace. When a navbox link to Wickham Terrace, Brisbane is viewed in Wickham Terrace it is not disabled. Downsize43 ( talk) 01:09, 22 August 2017 (UTC)
In theory, couldn't this be fixed by checking the redirectTarget of each linked page with the mw.title library? But it might not be desirable because it could use up too much of the expensive parser function quota on a page with a lot of navboxes. Toohool ( talk) 02:42, 23 August 2017 (UTC)
Hello I always get an error when using templates that rely on Module:Navbox. I get always this error: Lua-Feeler in Modul:Navbox, Zeile 241: attempt to index local 'listText' (a nil value). How can this bug be fixed? -- Soued031 ( talk) 11:50, 6 September 2017 (UTC)
Is it possible to do the following? If a page directly invokes
Module:Navbox, if the value at name=
does not equal {{BASEPAGENAME}}
, can the invoking template (but not the pages that transclude the template) be placed in a maintenance category?
Steel1943 (
talk)
22:33, 18 September 2017 (UTC)
I would like to have absolutely 100% control over all of the categories on my platform, but I cannot for the life of me prevent Navboxes from being automatically categorized. I have utilized |nocat=true, and while this has worked elsewhere, isn't doing a single thing to help on my created Navbox template. I would greatly appreciate any information on how to suppress these categories(or category handler altogether, if possible.) 2602:304:CF7D:A010:AC12:8F5E:4AC2:39B6 ( talk) 02:16, 26 September 2017 (UTC)
Should there be e.g. |groupnlang=
parameters? Are they necessary? I tried replacing an incorrect use of {{
lang}} (which uses a span tag) in {{
Irish names}} with |groupnstyle=" xml:lang="ga" lang="ga
but it doesn't seem ideal.
Jc86035 (
talk)
14:24, 24 December 2017 (UTC)
<div>...</div>
instead of <span>...</span>
with the lang tagging?
Frietjes (
talk)
14:37, 24 December 2017 (UTC)
|div=yes
?
Jc86035 (
talk)
14:40, 24 December 2017 (UTC)
I discovered that the wikipedia red link color on the standard navbox title color does not obey the WCAG 2.0 standards for text color contrast below 18pt. Not sure what to do about this. I started a discussion about this at WT:WikiProject Accessibility#Wikipedia red link on wikipedia standard navbox title violates WCAG 2.0, feel free to join in. — hike395 ( talk) 07:33, 3 January 2018 (UTC)
after changes to this module, the "old style" css borders no longer work as expected. The fix is to replace them with box-shadow borders like this. does anyone object to adding tracking to find these? I have put some code in the sandbox. Frietjes ( talk) 19:03, 8 January 2018 (UTC)
args = getArgs(frame, {wrappers = {'Template:Navbox|subgroup', 'Template:Navbox'}})
args = getArgs(frame, {wrappers = {'Template:Navbox subgroup', 'Template:Navbox'}})
args = getArgs(frame)
User:Johnuniq/sandbox2
into the "preview page with this module" box and Show preview. The idea of
Module:Arguments is to merge arguments from the invoking template and the parent wikitext, but that is usually unnecessary overhead. Therefore wrappers can be used to specify the templates which do not pass parameters (they merely wrap the module) and which therefore do not need merging. I can't understand the documentation for Module:Arguments so experiment would be needed to determine what would happen if a border parameter was passed in the parent wikitext as well as from the template.
Johnuniq (
talk)
02:30, 10 January 2018 (UTC)
border
from the template. I don't know if I ever tried that out last August, but I put it into
Module:Navbox/sandbox just now. Does that work?border
so my edit checks for that only. It should work!
Johnuniq (
talk)
02:48, 11 January 2018 (UTC)
%1
with item
using gsub. However, your code is good and I am just mentioning my thoughts for completeness. By the way, your script might be doing more than wanted: check
diff which changed "Carson–Newman" to "Carson to Newman". I might look at it more another time. There were quite a few problems when I converted a zillion articles using the system to the syntax preferred by {{
Football manager history}}. I could see the template might be useful in other cases but I was exhausted by then.
Johnuniq (
talk)
06:53, 12 January 2018 (UTC)