FANDOM


Support

Just want to say that I like this template, and I particularly like the fact that it's auto-collapsible. Support for its continued use. Will it fit in all screen resolutions?

Arosia (talk) 23:57, July 21, 2014 (UTC)

It's around the same size as other navboxes. I don't know how it looks under the default skin but if the others look good, this won't be any different. As long as the dash template is put on pages so that there will be no overlapping with the charinfo boxes, there shouldn't be a problem.
Shizune Hakamichi (talk) 00:11, July 22, 2014 (UTC)

Great. I can help make them. I have a lot of free time tonight, and I'm off tomorrow. I'll definitely get those CharNav templates added to the necessary pages tonight.

Arosia (talk) 00:18, July 22, 2014 (UTC)

Sure. I actually recommend just using the ones I've already changed as a base and replacing the names (ctrl-f replace all) and then changing the equip types if needed. This is easier than going into the existing source code and rewriting it manually, since there is a lot of legacy code that I removed. The problem is that we might need to search into what kind of equips are available to what chars in each game so they can be added appropriately, since we are missing a lot of those list pages.
Shizune Hakamichi (talk) 00:31, July 22, 2014 (UTC)
Not sure if you want to care about the default skin, but this is what I see. The game templates are not the most aesthetically pleasing though remain functional, but the character template's width hides the uncollapse button. Lanate (talk) 03:53, July 22, 2014 (UTC)

This is what I was worried about.

Arosia (talk) 03:55, July 22, 2014 (UTC)

The navboxes actually look like that? I never knew that the show/hide button overlapped with the text on the game templates. I'll shrink the width for this one by wordwrapping the links, since Cless, Reid, and Stahn are probably the only chars who have so many types of equips. And the Arche template is fine, unless the template width clips out of the visible space too?
Shizune Hakamichi (talk) 04:33, July 22, 2014 (UTC)
Arche's width is fine, I think. Lanate (talk) 04:46, July 22, 2014 (UTC)
These images are painful to see. I had no idea that there would be so much wordwrapping on the game navboxes for some users. I just now opened the page on IE (normally using Firefox) and see the text overlapping with the show/hide thing, but it's not doing the wrapping for the artes/titles parts for me... since I remember that I set the widths of the template and columns so that it wouldn't do that on either browser long ago. The easiest way to fix these is to widen the templates, but then that brings about the issue of possibly leaving the show/hide button cut off due to the width. This skin, always such an effective use of webpage margins.
Shizune Hakamichi (talk) 05:01, July 22, 2014 (UTC)

Does screen resolution have anything to do with it? I glanced at it while I was at work today and vaguely recall the show/hide button being hidden on my work computer, which is smaller than my home computer. This is why I initially posed the question. It appeared just fine when I checked it on my home computer, so I didn't think anything of it. I've always used the Wikia skin (it's what I've grown accustomed to, and I like to make sure things appear okay for all users), and I've never encountered the problem of not being able to see the button before (on either of my computers). This has been my issue as of lately in determining if page layouts appear acceptable in both minimum and maximum widths (adjustable in preview).

Arosia (talk) 05:10, July 22, 2014 (UTC)

For what it's worth, I run 1440x900 and these screens are from Chrome, but they appear similar in my Firefox, and both are at default text size. I browse with Monobook, so I don't notice things for the most part. Lanate (talk) 05:31, July 22, 2014 (UTC)

Full header bar collapsible toggle

In light of the above situation, I researched for a way to actually make it possible to click anywhere within the header bar to open/close the navbox. This result is actually kinda cool. Granted, I manipulated the code to make it -seem- like the whole bar is clickable, when in reality it's "99%" of the width, to circumvent an issue I found with the NavHead class in the MediaWiki CSS file. I basically modified the code from this topic, which actually has a very useful application for what I had wanted to accomplish with the individual arte pages when I was trying to set up a new layout for those.

Anyway, what does this mean? The entire header bar can now be used to open and close templates. The show/hide button still works, and actually it will reveal content instantly, whereas the header bar will animate its content scrolling up or down. This is the result of merging two different collapsible functions into the same code, and I wanted to keep the show/hide label so that it can still be visually intuitive that people can click to open the navboxes. But in the event that the show/hide label is hidden from view, the entire bar can still be clicked so that no functionality is lost. Basically, I'm just providing options for the sake of user accessibility, since that is also one of my objectives. Personally, I think the animated scrolling is kinda tacky, and I believe it is integrated into the mw-collapsible function so it cannot be changed.

I should note that a minor side-effect of merging two collapsible functions together like this actually can require more than one click in order to get the navbox to open or close, if the user alternates between the show/hide button and the rest of the header bar. This requires at most two clicks, even if someone tries to alternate between the two deliberately, and my testing doesn't show any way for this to break as far as I can tell.

Shizune Hakamichi (talk) 10:19, July 22, 2014 (UTC)

Incidentally, I did find a rather annoying thing to debug, the fact that the link to the char's own page was obscured by the new clickable field for collapsing the navbox and could only be right-clicked. This is no longer a problem. I've fixed it as well as I could, but there is now a small dead space to the immediate right of the char's name. I don't think this is a big issue compared to what I tried to do before I found that CSS elements can be layered, so I'm happy with the result. This dead zone isn't even that big, even with a string of text that is longer than Natnat's full name. I think these changes can be applied to all individual char templates now.

Shizune Hakamichi (talk) 13:23, July 22, 2014 (UTC)

Community content is available under CC-BY-SA unless otherwise noted.