Forum:Nav Templates

From the RuneScape Wiki, the wiki for all things RuneScape
Jump to: navigation, search
Forums: Yew Grove > Nav Templates
This page or section is an archive.
Please do not edit the contents of this page.
This thread was archived on 7 June 2010 by Aburnett.

I have noticed that some Navbox templates auto-collapse whereas some do not. I would like to make this more uniform, and simply have all of them collapse by default. This would make pages cleaner to look at, and people can still get to the information within by pushing a little "show" button. Not much else to say. Magic-icon.pngStelercusIlluminated Book of Balance.png 00:10, March 29, 2010 (UTC)


Support - As Nom. Magic-icon.pngStelercusIlluminated Book of Balance.png 00:10, March 29, 2010 (UTC)

Oppose - It's easier to see the information if it's not collapsed. It's much, much easier to miss that box if it's collapsed, since the show link is pretty small. The main reason that some templates are collapsed is because they're just simply too long. But, for things like {{Barbarian Assault}}, I think that we would be better off leaving it uncollapsed, where people are more likely to see it. --LiquidTalk 00:13, March 29, 2010 (UTC)

Weak Oppose - I prefer when they aren't collapsed personally, but I can see where them being uniform could help. But I see where Helium is coming from, and he has a really good point I think. HaloTalk 00:18, March 29, 2010 (UTC)

Comment - Just to clarify, navboxes are collapsed only if:

  1. They contain "collapsed" in the "state" parameter
  2. There are more than 2 navboxes in a page. The third (and subsequent) navboxes are collapsed automatically.
  3. If the height of a navbox is more 300 pixels.

Most of these settings already exist in Wikipedia, and I just implemented them here. The only thing unique for this wiki was the height autocollapse. As some of our navboxes were quite long, it made sense to me to autocollapse the really long ones (i.e. above 300 pixels).

The settings can be found in [[MediaWiki:Common.js]] in case they need to be changed. There is actually an "uncollapsed" state parameter for navboxes to force them NOT to collapse, but it is only partially implemented here.   az talk   08:41, March 29, 2010 (UTC)

Oppose - Per Liquidhelium. However, I would like to see some way of being able to opt-out of the max height autocollapsing. Some users like to use navbox based userpages but were unable to control the initial collapsed state of them because of this. The problem tends to show here since these navboxes tend to contain images/videos/large amounts of text as opposed to a set of links as is the case in mainspace navboxes. --Quarenon  Talk 16:35, March 29, 2010 (UTC)

I faced the same problem at War of Legends Wiki and I [ did this] to solve the problem there. With this fix, users would be able to "opt out" of any autocollapse by using the "uncollapsed" state parameter. When I noticed this discussion, I decided not to make the same changes here...
Can the navbox be fixed now, or should we wait for consensus?   az talk   16:53, March 29, 2010 (UTC)
That looks perfect. I think it would be fine to go ahead and merge those changes into our file now. Smile --Quarenon  Talk 17:08, March 30, 2010 (UTC)
Yes check.svg Done.   az talk   17:42, March 30, 2010 (UTC)
Er, can you give us less technical users a run-down of what's changed? --LiquidTalk 18:48, March 30, 2010 (UTC)
Basically I think it means that all tables auto-collapse now all the time unless explicitly specified otherwise. Hello71 00:47, March 31, 2010 (UTC)
No, nav-boxes still auto-collapse only if at least one of the three conditions Azliq mentioned above are satisfied. The only change is that you can disable auto-collapse by adding "uncollapsed" as part of the class name. See my sandbox for a working example.
In short, add class="uncollapsed" if you have a navbox that you don't want hidden by default. Navboxes behave the same as before if they don't use uncollapsed. It just adds more flexibility to the existing system that we use for auto-collapsing. Thanks Azliq for adding this! --Quarenon  Talk 01:46, March 31, 2010 (UTC)
Thanks for the clarification, Quarenon.   az talk   17:47, March 31, 2010 (UTC)

Uncollapse all - I don't mean to sound contrary, but I prefer when the navboxs remain shown rather than collapsed. Navboxes are always (or should be) at the bottom of a given article, so if someone doesn't want to read them, they just won't scroll down anymore. If someone does want to read them, collapsing them just slows things down. That makes sense to me. Do others disagree? Cheers, Air rune.png Tollerach hates SoF Fire rune.png 19:09, April 1, 2010 (UTC)

I do, purely for aesthetic reasons. I just dislike seeing a page where the navboxes are longer than the main article. Take for example Template:PVP items. The template is almost as long as the page it is used in, Zuriel's hood. Another example would be Template:Treasure trails rewards in the article Robin hood hat. The template is twice as long as the article. Looking at so many links at once is painful to the eyes, and makes us look like link farming site.   az talk   09:34, April 2, 2010 (UTC)

Support - I think the aesthetic reasons to do this outweigh the reasons not to do it. Ancient talisman.png Oil4 Talk 16:06, April 2, 2010 (UTC)

Support - If an infobox is so long that it needs to be collapsed, then it is too cluttered and needs to be cleaned up. White partyhat old.png C Teng talk 20:51, May 6, 2010 (UTC) Weak Oppose per Az. Some infoboxes should be collapsed. White partyhat old.png C Teng talk 20:53, May 6, 2010 (UTC)

Closed - Proposal will not be implemented at this time. --Aburnett(Talk) 19:35, June 7, 2010 (UTC)