Contents
- 1 Change of color
- 2 Width
- 3 Usability?
- 4 "need to be substed for the time stamp to work properly." What?
- 5 Documentation error - Around header text
- 6 Accessibility issue needs to be fixed.
- 7 Refactoring
- 8 merge template
- 9 Other wikis
- 10 How to pass partly red text to the custom warning message?
- 11 Works in IE, not Chrome?
- 12 Font colour
- 13 Weird
- 14 Unnecessary characters at front
- 15 Collapse all page after???
- 16 Import to another wiki?
- 17 Restrict namespace
- 18 max-width ?
- 19 Expand parameter not working
- 20 Left title alignment feature, for much better reading flow in prose
- 21 Wording
- 22 Font color for title
- 23 Relevant RfD
- 24 What does "expand=no" do?
Change of color
I changed the orange color to light green, because the former color is really too conspicuous for me to focus on reading real discussions hidden in the table box. (e.g. WP:SPI) If you think that the changed color is not desirable, feel free to change to any "neural color". Thanks--Caspian blue 23:36, 16 January 2009 (UTC)
Width
Extended content |
---|
Note, this template (AFAICT) gives no option to increase width. For those who want to widen the template, adding something like [[:File:Grey line.png|700px]] works. -Stevertigo 16:04, 19 March 2009 (UTC) |
Usability?
While collapse boxes save space, they actually impair usability in several major respects. For example the text within the collapse box is not searchable in the usual way, and clicking and entry in a table of contents no longer takes the user to a particular section if the section is collapsed. The template should be changed so that it says what the collapse box does: "The following content has been placed in a collapse box to save space." Short Brigade Harvester Boris (talk) 21:52, 22 May 2009 (UTC)
- Hi, can't you do that if you're an admin? --Caspian blue 22:03, 22 May 2009 (UTC)
- Hey CB, thanks for the response but I'm unclear on two points: (1) Do what? (2) I'm not an admin, so not sure what that part of your comment means. Short Brigade Harvester Boris (talk) 22:18, 22 May 2009 (UTC)
- I thought 1) you are waiting for other admin's input on this even though you can "do" the change of the text 2) The thought was based on my assumption that you're "of course" an admin (why don't you run for RfA? :)). Sorry for the confusion. --Caspian blue 22:26, 22 May 2009 (UTC)
- Actually I used to be an admin. But it wasn't fun. So I quit. Short Brigade Harvester Boris (talk) 22:41, 22 May 2009 (UTC)
- I thought 1) you are waiting for other admin's input on this even though you can "do" the change of the text 2) The thought was based on my assumption that you're "of course" an admin (why don't you run for RfA? :)). Sorry for the confusion. --Caspian blue 22:26, 22 May 2009 (UTC)
- Hey CB, thanks for the response but I'm unclear on two points: (1) Do what? (2) I'm not an admin, so not sure what that part of your comment means. Short Brigade Harvester Boris (talk) 22:18, 22 May 2009 (UTC)
"need to be substed for the time stamp to work properly." What?
Can anyone explain this from the /doc:
- {{Collapse top}}, or the redirect {{DAT}}, and {{Collapse bottom}} need to be substed for the time stamp to work properly.
Yes, I just edited it, but only for consistency with the /doc being shared, and DAT being used in the example above; I have no idea why it is so or if it currently is needed. Mark Hurd (talk) 08:29, 31 May 2009 (UTC)
Documentation error - Around header text
In Template:Collapse top#Around header text / "Replace with:" where it says
- {{subst:Collapse|Heading}}
shouldn't that read
- {{subst:Collapse top|Heading}}
? --- ToET 00:14, 6 September 2009 (UTC)
-
- I just found that error as well. The documentation seems to be wrong (WP:SPADE). I do wish "whoever has powers" would fix this to save a lot of research time. Thanks to whomever fixes it. --Aladdin Sane (talk) 04:08, 22 October 2009 (UTC)
Done, feel free to just fix it yourselves next time, template documentation is usually in a subpage and not protected. Amalthea 08:18, 22 October 2009 (UTC)
- Thanks. I admit I missed the edit links in the docs. The "Edit this page" tab being missing, I failed to look more closely. —Aladdin Sane (talk) 12:48, 22 October 2009 (UTC)
- I just found that error as well. The documentation seems to be wrong (WP:SPADE). I do wish "whoever has powers" would fix this to save a lot of research time. Thanks to whomever fixes it. --Aladdin Sane (talk) 04:08, 22 October 2009 (UTC)
Accessibility issue needs to be fixed.
{{Editprotected}} The font size reduction is too much for some readers even as-is, but when this template is used inside another that already had a reduced font size (e.g. a {{todo}}), it's just a killer, as the 10% font size reduction becomes 20% and so on. The problem is that this template recycles CSS classes intended for navboxen, when this is not a navbox and is not meant to actually look like one. The fix I have implemented overrides the font shrinking and (in the browsers I've tried so far) keeps the text at exactly its original size (inside another shrinking template such as a todo list the text inside this template will be the same size as the rest of the text in the todo box or whatever).
I have fixed this at {{Collapse}}; you can just copy-paste the div font-size code (2 occurrences).
PS: I don't think this needs some protracted consensus discussion, as the shrinkage effect is almost certainly an unintended consequence of the class used, and a severe WP:ACCESS problem like this trumps editorial whims. Also, the change can't really have any negative effect, since all it does it stop a cascade of ever-shrinking font sizes. — SMcCandlish Talk⇒ ʕ(Õلō)ˀ Contribs. 15:21, 17 January 2010 (UTC)
Done. I didn't see the need to use a div though. I set the fontsize on the tablecell instead. —TheDJ (talk • contribs) 20:55, 17 January 2010 (UTC)
Refactoring
I have added this text:
- In line with with the Wikipedia:refactoring guideline, if an editor who comments are included in a collapsed discussion objects to the use of this template to alter the look of a talk page, then it should not be used.
under a section called "General information". As the Wikipedia:refactoring guideline says
- Refactoring is a form of editing whose goal is to improve readability while preserving meaning. It is a stronger term than copy editing and can include removing superfluous content, summarizing long passages, and any other means that alter the presentation of information.
Which is I think a fair description of the use of this template on talk pages when it is used to alter the look of a talk page by collapsing a conversation and as the refactoring guideline goes on to say:
- Refactoring should only be done when there is an assumption of good faith by editors who have contributed to the talk page. If there are recent heated discussions on the talk page, good faith may be lacking. If another editor objects to refactoring then the changes should be reverted.
I think this addition is justified as it resolves any potential edit-war on the talk page by reverting to the status quo. -- PBS (talk) 10:31, 1 March 2010 (UTC)
merge template
{{editprotected}}
could someone add a {{mergefrom}} template to this page, please? put the following at the top of the page: <noinclude>{{mergefrom|Template:Hidden archive top}}</noinclude> This merger will require modification of this template, and a merger of templates {{cob}} and {{hab}} as well. --Ludwigs2 16:34, 1 March 2010 (UTC)
Other wikis
What do I need to do to get this to work on my wiki? See http://libertarianwiki.org/Template:Collapsetop 161.98.13.100 (talk) 02:48, 17 March 2010 (UTC)
- You need to add some code to your Wikimedia:Common.css and Wikimedia:Common.js file. I added this change to :no:MediaWiki:Common.js (you will probably not rename show/hide as I did there) and this change to :no:MediaWiki:Common.css at the Norwegian wiki to get it running. Nsaa (talk) 13:09, 30 March 2010 (UTC)
The explanation is at mw:Manual:Stealing_content_from_Wikipedia. Tisane (talk) 15:50, 30 March 2010 (UTC)
How to pass partly red text to the custom warning message?
This {{cot|custom warning|this is a custom warning line that will do your <span style="color:blue;">'''face blue'''</span>}} do not work:
custom warning |
---|
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. |
- Interesting... I'm not sure why that doesn't work, and I'll look into it, but in the meantime here's a workaround using {{color}}:
{{cot|custom warning|this is a custom warning line that will do your {{color|blue|'''face blue'''}}}} {{lorem ipsum}} {{cob}}
custom warning |
---|
this is a custom warning line that will do your face blue |
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. |
- --Ludwigs2 17:21, 30 March 2010 (UTC)
- I believe the problem is the "=" sign in an unnamed parameter. Try using {{cot|custom warning|2=this is a custom warning line that will do your <span style="color:blue;">'''face blue'''</span>}} instead. Plastikspork ―Œ(talk) 18:03, 30 March 2010 (UTC)
custom warning |
---|
this is a custom warning line that will do your face blue |
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. |
Works in IE, not Chrome?
This is my experience. Thoughts? — Timneu22 · talk 21:10, 15 June 2010 (UTC)
- Are you referring to this? Plastikspork ―Œ(talk) 21:43, 15 June 2010 (UTC)
- Precisely. Mmmph. Pretty sure these things used to work. Is that where I should follow the discussion (I realized it wasn't specifically this template's issue)? — Timneu22 · talk 22:59, 15 June 2010 (UTC)
- I would say so. It seems to be a broader issue. Thanks! Plastikspork ―Œ(talk) 17:12, 23 June 2010 (UTC)
- Precisely. Mmmph. Pretty sure these things used to work. Is that where I should follow the discussion (I realized it wasn't specifically this template's issue)? — Timneu22 · talk 22:59, 15 June 2010 (UTC)
Font colour
Can a parameter be added for the font colour of the heading? Hazard-SJ Talk 22:52, 15 August 2010 (UTC)
- You can achieve this now by overloading the background colour parameter (see wikitext):
Heading |
---|
Text |
- It's a bit of a hack, but it works. Plastikspork ―Œ(talk) 01:37, 17 August 2010 (UTC)
Weird
Hi. Have a look at the collapsible template at Template:Infobox power station/doc#Parameter names and descriptions, and full syntax. Any idea why the template headers change colours when added to the collapse template? Rehman(+) 12:05, 24 October 2010 (UTC)
- I'm not seeing that happening. what browser are you using? --Ludwigs2 14:57, 24 October 2010 (UTC)
-
-
- On up-to-date versions of Safari (5.0.2) and Firefox (3.6.6) on a Mac, the template headers are the same color (dark gold). Unfortunately, whoever wrote this tempalte didn't use the standard {{infobox}} format, so it's a pain to diagnose. I'll bet that if you converted it to the standard format, the problem you're seeing would go away. --Ludwigs2 16:05, 24 October 2010 (UTC)
-
-
-
-
-
- Ah, I see. well, this is probably caused by the template inheriting the 'Navbox' class of the table that makes {{collapse top}} work. you might be able to fix it by monkying with the class of the infobox table to prevent inheritance, but (as I said above) the better approach would be to convert this mess to standardized {{infobox}} format. --Ludwigs2 01:13, 25 October 2010 (UTC)
-
-
-
-
-
-
-
-
- Well, the genius behind that mess is me ;) I will see what I can do to turn the template to the standard format, as I never came across it before. The template is pretty much inherited from {{Infobox dam}}; and took me about a month to get it working. So would take another month or two to convert it again. ;) Kind regards. Rehman(+) 09:38, 25 October 2010 (UTC)
-
-
-
-
-
-
-
-
-
-
- No, it will take you 15 minutes or so to familiarize yourself with the format, and 30 minutes to an hour to do the conversion. it should work first or second draft. The only two gotchas are
- keep in mind that you can't have headers and label/data with the same index (the header will cancel out the label/data). so, if you use
|header5=
, you'll want to use|label6=
and|data6=
- try to leave yourself a little wiggle room. you can use index numbers up to 80, they don't need to be in sequence, and it's a pain to readjust all the index numbers to add new parameters, so skipping a couple of index numbers before each header (or at other likely points) makes updating the template much easier in the future.
- keep in mind that you can't have headers and label/data with the same index (the header will cancel out the label/data). so, if you use
- I'll take a look at converting infobox dam, myself. --Ludwigs2 16:22, 25 October 2010 (UTC)
- No, it will take you 15 minutes or so to familiarize yourself with the format, and 30 minutes to an hour to do the conversion. it should work first or second draft. The only two gotchas are
-
-
-
-
-
-
-
-
-
-
-
-
- Thanks. I will handle the {{Infobox power station}} soon. Kind regards. Rehman(+) 00:30, 26 October 2010 (UTC)
-
-
-
-
-
-
Finished converting both infoboxes, and guess what, the collapsible template at the end of the doc page still alters the left-column background colours. I just upgraded my Firefox to 3.6.12, still the same. It's not much of an issue at the power station infobox, but it may be worth fixing in other cases... Rehman(+) 01:16, 31 October 2010 (UTC)
- Eh, I went ahead and fixed it the old fashioned way. --Ludwigs2 03:26, 31 October 2010 (UTC)
Unnecessary characters at front
{{editprotected}}
At the start of this template are the characters {<noinclude></noinclude>
. The <noinclude>
tags don't surround anything and thus are spurious; additionally, unless I am badly mistaken (EDIT: I am), the initial Thus I would recommend removing the initial {
character appears to be unbalanced.<noinclude></noinclude>
. Actually, the initial {
is balanced out in {{collapse bottom}}
. Reaper Eternal (talk) 00:39, 6 March 2011 (UTC)
- That big chunk of code in the beginning just expands out to {|. I haven't a clue why it's so elaborate, but I'd rather not yet touch it myself. Magog the Ogre (talk) 02:47, 6 March 2011 (UTC)
- Some of the other code looks as though it could be shortened as well. I've placed a tidied up version in Template:Collapse top/sandbox if anyone cares to look. -- WOSlinker (talk) 17:03, 6 March 2011 (UTC)
- Nice work, I have implemented the change. Thanks! Plastikspork ―Œ(talk) 21:19, 6 March 2011 (UTC)
- Some of the other code looks as though it could be shortened as well. I've placed a tidied up version in Template:Collapse top/sandbox if anyone cares to look. -- WOSlinker (talk) 17:03, 6 March 2011 (UTC)
Collapse all page after???
was going to use this on the kings island page to colaps a table, but it colapses the entire page after colapse top, not just to colapse bottom. Maybe a conflict with a navbox at the bottom of the page? see here. how to fix this? --Nickvet419 (talk) 08:09, 19 March 2011 (UTC)
got it, collapse bottom need to be on its own line.--Nickvet419 (talk) 08:18, 19 March 2011 (UTC)
Import to another wiki?
If I want to import this template to another wiki (well, I've done it and it doesn't work) what else do I need to do? I'm suspecting that the class="navbox collapsible" stuff needs to come too: where does that live? William M. Connolley (talk) 10:17, 6 April 2011 (UTC)
- http://en.wikipedia.org/wiki/MediaWiki:JQuery-makeCollapsible.js
- http://en.wikipedia.org/wiki/MediaWiki:JQuery-makeCollapsible.css
- I know this is used in the show/hide functionality. Reaper Eternal (talk) 10:41, 6 April 2011 (UTC)
- Thanks for the help. I tried importing those too, but it wasn't enough. I think I'll try talking to my admin - possibly the mediawiki I'm using needs an upgrade (perhaps a clue is that when I view those js/css on my wiki, they don't format nicely as they do here) William M. Connolley (talk) 20:39, 6 April 2011 (UTC)
Bump. Could some guru point me to the instructions on how to import the cot/cob templates to another wiki? --Surturz (talk) 05:14, 8 May 2013 (UTC)
Restrict namespace
Can we restrict this so it cannot be used in articles? It is structured in such a way that it will not show in the print version. For example, try the "printable version" of this page. For this reason, I think it should only be used on user pages and talk pages, but restricting to non-articlespace would be a start. Frietjes (talk) 22:26, 8 April 2011 (UTC)
- Can the print stylesheet be modified so that the CSS class used by this template is displayed instead of hidden? That would probably be easier. Jehochman Talk 14:26, 9 April 2011 (UTC)
- It uses the navbox class, which is hidden in print. We definitely don't want to change that, since large chunks of navigation links aren't useful in print. To restrict it from articles, we would just need to add some thing like
{{main other | ... existing code ... | <span class="error">This template should not be used in articles ... </span> }}
-
- which would warn editors of what went wrong. It doesn't look like it has been used very frequently. Per MOS:COLLAPSE, I don't know why we need it in print anyway. The larger problem is that editors use the {{navbox}} template to do exactly the same thing. Thanks! Plastikspork ―Œ(talk) 14:32, 9 April 2011 (UTC)
max-width ?
Is there any possibility a max-width parameter could be added that would accept percentages as values? Cloveapple (talk) 05:47, 26 August 2011 (UTC)
- You could probably do this now by overloading the "indent" parameter, say "indent=0px; max-width: 50%", but a better idea would be to add a separate "style" paramter. Frietjes (talk) 20:11, 26 August 2011 (UTC)
- Thanks. I don't understand template coding enough to add a new parameter myself, but I'll try using the indent parameter and see what happens.Cloveapple (talk) 00:17, 27 August 2011 (UTC)
Expand parameter not working
I've copied the "Template:Collapse top" and "Template:Collapse bottom" to my user space on another wiki. Everything works as expected except that when the page loads the collapse box is uncollapsed / shows / is open by default. Once it has loaded, then I can show or hide the box by clicking the link and it works just fine.
As I understand it, the box should be collapsed by default when the page loads. No amount of my attempting to fix the problem has worked. Leaving the expand parameter out of the parameter list, setting the expand parameter to false, and setting the expand parameter to 0 all fail to collapse the box. Though I've modified the original template code to fit my needs in my user space, I've also tested an unmodifed version of the template copy-pasted directly off the wikipedia page into my user space and still get the same behaviour. In other words, the problem I'm having isn't due to an error introduced through my modifications; it happens even when the template hasn't been edited by me.
This is the template code I copied from wikipedia, pasted into my user space, and was able to make work successfully with the exception of the default expand-collapse issue noted above:
<div style="margin-left:{{{indent|0px}}}"><!-- NOTE: width renders incorrectly if added to main STYLE section--> {| <!-- Template:Collapse top --> class="navbox collapsible {{{{{|safesubst:}}}#if:{{{expand|}}}||collapsed}}" style="background: transparent; text-align: left; border: {{{border|1px}}} solid {{{b-color|silver}}}; margin-top: 0.2em; {{{{{|safesubst:}}}#if:{{{width|}}}|width:{{{width}}};}}" |- ! style="background-color: {{{bg|#CFC}}}; text-align:center; font-size:112%;" | {{{1|{{{title|{{{reason|{{{header|Extended content}}} }}} }}} }}} {{{{{|safesubst:}}}#if:{{{warning|{{{2|}}}}}} |{{{{{|safesubst:}}}!}}- {{{{{|safesubst:}}}!}} style="text-align:center; font-style:italic;" {{{{{|safesubst:}}}!}} {{{2|The following is an archived debate. <span style="color:red;">'''Please do not modify it.'''</span>}}} }} |- | style="border: solid {{{border2|1px silver}}}; padding: {{{padding|8px}}}; background-color: {{{bg2|white}}}; font-size:112%;" {{{{{|safesubst:}}}!}}<noinclude> {{lorem ipsum|3}} {{Collapse bottom}} {{Documentation}} <!-- PLEASE ADD THIS TEMPLATE'S CATEGORIES AND INTERWIKIS TO THE /doc SUBPAGE, THANKS --> </noinclude>
I don't know if this would have any relevance, but I'm viewing the page in IE 8 (32-bit version) on a Windows 7 64-bit machine. But I'm able to see the template work correctly on the wikipedia page devoted to "Template:Collapse top", so it doesn't appear to be a browser-related issue. Thank you in advance for any assistance any one is able to offer. CCB2011 (talk) 05:33, 13 December 2011 (UTC)
- If I'm not mistaken, the collapse template makes use of some Javascripts local to English Wikipedia. Your problem might lie in that the other wiki doesn't have the right Javascripts, or has them installed for different parameters. WP:VPT would be a good place to ask. Magog the Ogre (talk) 08:18, 13 December 2011 (UTC)
-
- Check the project and skin CSS files as well. Collapsible Navboxes work by using javascript to hide and show table columns via css. If you don't have the right css classes (or if you have the cascade set up the wrong way) that can monkey-wrench them. --Ludwigs2 14:25, 13 December 2011 (UTC)
-
-
- Thank you, Magog and Ludwigs, for your responses. The other wiki is indeed using the installed JavaScripts with different parameters. They have a different implementation of a collapse box on that site and, with assistance from an admin, I've finally been able to find a Template that works. CCB2011 (talk) 00:53, 25 December 2011 (UTC)
-
Left title alignment feature, for much better reading flow in prose
A new feature for left alignment of title has been installed, in the Template:Collapse top/sandbox, and tested in the Template:Collapse top/testcases subpages.
The new feature's documentation for the Template:Collapse top/doc page:
...
- 'left'
- If this parameter evaluates to true (i.e. is not empty), the title will be aligned left instead of centered, for better reading flow in prose, e.g. template documentation. It has no effect on the position of the box. There's no corresponding 'right', as there's no need for it, and it would interfere with the position of the "show/hide" button.
I've been having to painstakingly simulate this with |title=<div style="text-align: left;">Title here</div>
at templates like Template:Blockquote paragraphs because the centered text, while appropriate for warnings and notices, is quite reader-annoying when the template is used, for example, to hide blocks of boring source code test cases in the middle of documentation that someone's reading.
I've also fixed the problem that "heading" wasn't a synonym of "title".
Also simplified the red-bold warning code. We have a template for that, at {{strongbad}}
, so no need to do it with manual span and CSS (also has the benefit of using the semantically correct <strong>...</strong>
markup, instead of the purely typographic boldfacing of <b>...</b>
, which is what MediaWiki's '''...''' boldfacing resolves to.)
Example demonstrating all three changes:
Boring flamewar |
---|
The following is a closed debate. Please do not modify it. |
Code: {{Collapse top/sandbox|expand=y|left=y|heading=Boring flamewar|warning=y}} |
— SMcCandlish Talk⇒ ʕ(Õلō)ˀ Contribs. 08:14, 3 February 2012 (UTC)
Done And protected {{strongbad}} and {{strong}} for you, to prevent template vandalism since they are now used in this widely-used template. Anomie⚔ 21:10, 3 February 2012 (UTC)
Wording
I have changed archived to closed as it is in Template:Hidden archive top it was agreed on the talk page there that "archive" was not correct because archive has a specific meaning as in WP:ARCHIVE and that close was more appropriate. I would also suggest that the wording on {{Hat}} "This discussion has been closed" is more elegant than the phrase here "The following is a closed debate" and would suggest replacing the latter with the former. -- PBS (talk) 23:45, 7 February 2012 (UTC)
- Was thinking of that myself. You saved me from lodging another editprotected request. :-) — SMcCandlish Talk⇒〈°⌊°〉 Contribs. 07:51, 16 February 2012 (UTC)
Font color for title
color: {{{fc|black}}}
By adding the code above for the title style. As seen on the test cases, I have added fc as a arg value so when background colors are so bad for the black text it can be changed.—CKY2250 ταικ 22:18, 13 November 2013 (UTC)
Question: Cky2250, I see that your edit removed the
{{{bg1}}}
parameter.[1] Is this intentional? — Mr. Stradivarius ♪ talk ♪ 23:28, 13 November 2013 (UTC)- Pinging because I messed up the first notification: Cky2250. — Mr. Stradivarius ♪ talk ♪ 23:32, 13 November 2013 (UTC)
-
-
-
Done. Glad we straightened that one out. :) — Mr. Stradivarius ♪ talk ♪ 09:02, 14 November 2013 (UTC)
-
-
Relevant RfD
An RfD is being held that may affect templates similar to this one: See Wikipedia:Redirects for discussion/Log/2014 February 15#Template:Cop. —/Mendaliv/2¢/Δ's/ 02:13, 16 February 2014 (UTC)
What does "expand=no" do?
Currently, |expand=no
expands the box. That is because it has code <code> #if:{{{expand|}}}||collapsed}}</code>. The documentation says: "If this parameter evaluates to true (i.e. is not empty) ...". That may be correct, helpful it is not. I suggest changing that behavior:
|expand=yes
inyes, y, YES, Y, 1
expands.
All other values & settings (including: <blank>, omitted, + default behaviour) then do expand=no
.
Code proposal (subst: requirements omitted here):