Is there the capability to modify this template so that its sections could be collapsible? The
Style template is very long and awkward, and collapsibility would make it much more convenient. Regards,
Waltham,
The Duke of12:32, 3 May 2008 (UTC)reply
I'm concerned with the issue for a little while. The problem that we face is too much MoS sections and guidelines. They overlap each other and form a nice
instruction creep. I don't think that what you are proposing is a solution to the problem. What would you say about deleting the project-specific links from the {{Style}} (e.g. anime, US highways, etc...)? --
Kubanczyk (
talk)
20:29, 25 May 2008 (UTC)reply
Not done: please be more specific about what needs to be changed. Could be tricky... why don't you try in a sandbox first and come back with some code?
Happy‑
melon19:47, 10 August 2008 (UTC)reply
Stacking boxes
How do I get two helpboxes to go one under the other? For example, I want to get {{Policy list}} followed by {{Guideline list}}, both on the right of the page; but when I just call the templates one after the other I see them next to each other instead of stacked vertically.--
Kotniski (
talk)
09:04, 18 July 2008 (UTC)reply
Since no-one could answer that, I've created a new template, {{Helpbox stackable}}, for which the above behaviour works (I added class="infobox vcard" - I have no idea why this works, since I can't find the class definition in any css file, but it seems that it does work).--
Kotniski (
talk)
12:07, 19 July 2008 (UTC)reply
As part of an ongoing project to get the dozens of different sidebar meta-templates we presently have singing from the same hymn sheet, I've rewritten this template as a wikitable. Other than code readability, I've also added the navbox-vertical class for semantic value and added clear: right so that this no longer ends up floating in entirely random locations when it's stacked with other sidebars. If there are no objections I'll sync this in a few days.
Chris Cunningham (user:thumperward: not at work) -
talk17:47, 7 September 2010 (UTC)reply
If you are going to re-instate the changes please ensure that the net visual effect on the rendered page (in e.g. {{dispute-resolution}}) remains as close to the original as possible, especially in terms of width of the box and font-size. –
xenotalk15:54, 8 November 2011 (UTC)reply
I have reverted these modifications because it is causing formatting errors on
Template:Naming conventions. Specifically, it is ignoring {{{1}}} being set to "width:300px;" on many browsers and wide-screen monitor resolutions, and instead defaulting as if no width is ever specified (See new example on
Template:Helpbox/testcases; the widths are not equal when viewed on a wide-screen monitor resolution.
[1] . Please test and make the necessary modifications before reinstating. Thanks.Zzyzx11 (
talk)
05:03, 21 November 2011 (UTC)reply
I think I found the bug. {{#if:{{{1|}}}|{{{1}}}}}; needs to appear last in the "style" parameter if one wants to override one of the "background-color: #f5faff; font-size: 90%; width: auto; line-height: 1.6em;" CSS attributes.
Zzyzx11 (
talk)
06:00, 21 November 2011 (UTC)reply
This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.
Please update with the version currently (as of this message) in the sandbox
here. From the revision history: (removed duplicate heading12/content12 entries then replaced headingN/contentN with heading(N+10)/content(N+10) in order to use content1 to place spacer between title and template's contents). In other words, a gap between the title and first heading is the only (substantial) change. Thank you,
Sardanaphalus (
talk)
12:19, 20 May 2014 (UTC)reply
Thank you – and for display:block;margin-bottom:N, which looks like something useful to know. Perhaps it might be added as optional styling to {{Sidebar}} itself, activated e.g. by |spacer=on and/or |titlebodyspacer=on, ...?
Sardanaphalus (
talk)
08:28, 22 May 2014 (UTC)reply