Admin Forum:Weird positioning of Edit/Facebook/Comments buttons on blog pages

I dunno that much about blog page coding peculiarities, which means I'm baffled by something going on at all blog pages at w:c:tardis. For some reason, the edit, facebook, and comment buttons are all off to the right side of the page. Here's a link to a typical blog post. Not sure if you'll be able to see the edit button since it won't be your page, but you should still see the "slide" on the facebook and comments stuff. Feel free to make a test blog post.

Even the smallest tidbit of experience with styling blog pages would probably be helpful to understanding this odd behavior I seem to have unwittingly created. 15:30: Thu 12 Apr 2012


 * The problem is this code in the MediaWiki:Wikia.css:


 * makes the header section of blogs so wide that it extends into the siderail and beyond.
 * Incidentally, the Monobook skin on that wiki is broken (screenshot). --Gardimuer { ʈalk } 19:03, April 12, 2012 (UTC)


 * Monobook looks okay for me on FireFox 11 (Win7x64), but I'll try it on Safari on my MacBook Pro. Maybe it is a browser issue. -- Fandyllic (talk &middot; contr) 12 Apr 2012 4:51 PM Pacific


 * CzechOut fixed it.
 * On a side note, I have some suggestions that don't have anything to do with the question.
 * You've made really nice themes for both the Monobook and Oasis skins. However, I get significant performance drops in Firefox whenever I view pages on that wiki- especially in the Monobook skin. This is because you are using a lot of box shadows in your design. That kind of styling is a heavy drain on the browser's resources when rendering a page, and when that drain is too much it causes noticeable lag when a viewer scrolls up and down a page. Depending on browser type and the graphics rendering power of a person's computer, not every visitor will experience this performance drop. It's up to you whether you want to do anything about this. From my past experience with lag problems on the BioShock Wiki, I recommend reducing the amount of box-shadow styling in your design.
 * Another minor suggestion: I notice that you have some extremely long CSS comments in MediaWiki:Common.css. The extra characters in those comments cause the CSS to be a larger file, which could affect page load times. It would be more efficient to put that information in MediaWiki talk:Common.css. --Gardimuer { ʈalk } 00:29, April 14, 2012 (UTC)
 * Thanks, guys. A lot of good stuff there!  03:42: Sat 14 Apr 2012
 * Okay, I've heard this criticisim before that I should be reducing box-shadow. Which sucks, because I think it's a great design tool.  But anyway, the thing I've never quite wrapped my mind around is how I get some objective, quantifiable measure of performance.  What's the metric that's used to test for performance?  What's the part of Firebug/Safari page inspector/Opera Dragonfly that I use to test for performance?  That's probably a pretty basic question, but somehow that knowledge has passed me by.   14:04: Sat 14 Apr 2012
 * Alrighty, I think I've massively improved the speed in Monobook by removing the inset box shadows (except for a few instances of "accents"). Coudl someone who was actually seeing performance issues please return to w:c:tardis and check out whether I've been successful?  Thanks.  :)  18:07: Sat 14 Apr 2012


 * I just checked out the Monobook skin again, and the scrolling is significantly smoother after your adjustments. I've never personally tested any performance measurement tools, but you might find this utility useful: "CSS Stress Testing and Performance Profiling" --Gardimuer { ʈalk } 23:25, April 14, 2012 (UTC)