Template talk:Apinav

= From User talk: Starlightblunder =

Why did you remove float, and refer to parent templates? What did you mean? This may be called by other templates, but at least on one page it's not. Schmidt 18:27, 17 June 2006 (EDT)


 * Good point, should leave it / fix it in the page that calls it directly. The basic issue that I'm trying to correct is that the top 400ish pixels of every API pages will get taken up by the menu -- something that isn't directly relevant once you've come that far down the tree. The change I'm suggesting is adding a float:right and the fixed width on the entire thing, through the parent templates (likes of wowapi). Can't do that directly from Template:Apinav because the footer text added by wowapi and framexml would look out of place. Still working through the templates, though -- you've startled me midedit :). Starlightblunder 18:32, 17 June 2006 (EDT)


 * Heads-up: API_Frame_SetBackdropBorderColor looks a bit cramped. --Mikk 18:57, 17 June 2006 (EDT)
 * Internet Explorer-specific, too. It seems that tags and float: right don't live together very well. It can be resolved by using
 * content to be centered
 * instead of the center tags (which are deprecated, and should be avoided anyway), but replacing that into every single API page seems a bit nasty. Any suggestions? -- Starlightblunder 19:14, 17 June 2006 (EDT)


 * I wasn't thinking about that as much as the function name linewrapping, and the [Edit] boxes getting glued to the side of the menu. I'm no big fan of those "written by" thingies anyway. It's a wiki for god's sake. Lots of people contribute to any one page. --Mikk 19:18, 17 June 2006 (EDT)


 * I agree with your view on the "written by" notices -- thought you were referring to that since it's the major render issue on the page. The issues you've described can be resolved with a bit of tweaking: we can get the [Edit] links unstuck by adding a margin: declaration to the outer div, and the wrapping by increasing the div's width. Applied those two tweaks to widgetmethod -- seems to work as intended. Starlightblunder 19:27, 17 June 2006 (EDT)


 * Thinking more about apinav, though: removing float:right there doesn't make a significant difference to how it appears in other pages, as the element had no specified width (and thus expanded to fit the page). It's also somewhat comforting to know that the amount of vertical space eaten by the float bug is not more than what would have been eaten if it we didn't make the change. Starlightblunder 19:14, 17 June 2006 (EDT)

= From User talk: Mikk =

Problem is, removing the fixed width declaration on wowapi causes the div / table to take up the entire page: API_GetSubZoneText. This wastes the first screen on smaller resolutions, and float:right becomes useless -- isn't it better to leave the fixed width declaration in? Starlightblunder 08:41, 18 June 2006 (EDT)


 * Huh? On what browser? --Mikk 08:42, 18 June 2006 (EDT)


 * IE6. Render shot. Starlightblunder 08:46, 18 June 2006 (EDT)


 * Duh yeah, I just saw it. It shouldn't do that though, I have floats working in IE6 in other places of the wiki. Let me test a couple of things... --Mikk 08:48, 18 June 2006 (EDT)


 * Fixed. Replaced ""s (&lt;hr&gt;s) with divs with a border-bottom. Works. --Mikk 08:50, 18 June 2006 (EDT)

= See also =


 * Template talk:Wowapitype