Template talk:Rare materials nav

Just me or is this box too wide? Fox 21:25, 11 March 2007 (EDT)
 * It's the same width as every other nav box on the wiki, and 4% smaller than the original nav box style. It's probably the nowrap tags though. I'll take them out and tell me if it's any better. - B e X o R  21:34, 11 March 2007 (EDT)


 * Sorry for late reply :/ Yes, that's wunderbar :) Fox 09:28, 12 March 2007 (EDT) Added: I noticed there was an apparently redundant  after Vial of Ink; I removed it, and don't think I broke the template :S Fox
 * And I noticed another one hehe. - B e X o R  01:01, 13 March 2007 (EDT)
 * I really don't like fiddling too much with templates in case i am missing a grasp of the arcanes runes of CSS and screw it up! But I have put in 2 x  to force the Elonian leather image to sit next to the related text and ditto Roll of vellum. I'm not sure if   is the right thing to use, but it seems to work. Anyway, the template is great. Gj! Fox 04:23, 13 March 2007 (EDT)
 * that  seems to be no real help. Is there any way to make icon + name of material inseparable? When you change browser size, one after another jumps to next line, icon later than text. - MSorglos 04:33, 13 March 2007 (EDT)

(Reset indent) Hm, good point Msorglos, I just moved up the text size and it all went askew again. Hadn't thought of that :P I don't know if they can be forced to stay together, I'll have to delve into the runes and see what it says.... Fox 05:09, 13 March 2007 (EDT)
 * I can force them to not separate, but it's a lot of unwieldy code. If you can tell me which ones specifically are breaking up, I can just apply the code to those, rather than doing it to the entire table. - B e X o R  06:19, 13 March 2007 (EDT)
 * If you use Browser windowed and change width it can happen to every entry. Tested with IE7 and Opera 9.1 - MSorglos 06:30, 13 March 2007 (EDT)


 * I thought an &amp;nbsp; might do the trick, but it won't. You could do it with CSS and lists, but it would be difficult to make it look exactly the same. LordBiro 06:54, 13 March 2007 (EDT)


 * Well it wouldn't happen to the first in the list, cause who browses with a window 2 inches wide? I'll work on it after I have dinner. :P - B e X o R  07:01, 13 March 2007 (EDT)


 * This template seems to work for IE now, but not for Opera. I have one line with all entries after Amber in one row. - MSorglos 05:27, 15 March 2007 (EDT)
 * Try it again in Opera. It will probably just have them all in 1 row. - B e X o R  05:32, 15 March 2007 (EDT)


 * Yes, all in one row now. But better than to have Amber in extra row - MSorglos 06:07, 15 March 2007 (EDT)


 * Does that mean it looks ok, or is it off the screen horizontally? - B e X o R  06:08, 15 March 2007 (EDT)

(reset ident)

It is better than Amber on one row and the rest on the other row. But it is off the screen horizontally, no little line break. Almost double screen width on 1200x800. - MSorglos 07:53, 15 March 2007 (EDT)


 * Well we can either have it like this, or with the line breaks in random places that separate the picture and text like it was before. I would suggest we go back to that for the sake of those who use Opera. - B e X o R  07:56, 15 March 2007 (EDT)


 * is there any way to force Opera to possible line break between that span tags? - MSorglos 08:25, 15 March 2007 (EDT)


 * Tried a new method. Shows correctly in Firefox, sometimes the words disappear in IE, but I'll work on that. How does it look in Opera? - B e X o R  03:08, 16 March 2007 (EDT)


 * No changes in Opera, still all in one row - MSorglos 04:13, 16 March 2007 (EDT)


 * Okay, looks like we'll have to deal with having the word split from the image. The bullet points should be indication enough of matching image and text. The code that stops the line from splitting up when it encounters any white space is causing too many problems to be worth using. If you notice this problem anywhere else let me know. - B e X o R  04:25, 16 March 2007 (EDT)


 * Perhaps another possibility is to do that Template fixed size such as Template:Materials_nav. Would consume little more space (perhaps 4 rows?) but would look same in every browser. - MSorglos 07:13, 16 March 2007 (EDT)


 * It would cause problems for different resolutions. I think the best option is to just have it the way it is. It doesn't take much more than common sense to figure out which picture belongs to which name. - B e X o R  07:43, 16 March 2007 (EDT)