html - Tumblr: Content Overlaps Fixed Header? -

i able code fixed header tumblr blog: http://artsypancake.tumblr.com/

the header works fine on home page , overlaps of posts, intended effect. however, content on custom pages runs on header when scroll down. example: http://artsypancake.tumblr.com/aboutme confusing occurs custom pages i've made.

also, i've tried increasing z-index header, doesn't make difference on custom page posts.

here's css header:

#topbar { z-index: 999; position: fixed; top: 0; left: 0; width: 100%; height: 27px; text-align: center; background-color: {color:top bar background}; border-bottom: 3px solid {color:top bar border}; }  #topbar { position: relative; font-family: text me one; color: {color:top bar text}; background-color: {color: top bar text background}; letter-spacing: 1px; font-size: 9px; text-transform: uppercase; margin: 5px; padding: 5px; top: 7px; -webkit-transition: 0.2s ease-in-out; -moz-transition: 0.2s ease-in-out; -o-transition: 0.2s ease-in-out; -ms-transition: 0.2s ease-in-out; transition: 0.2s ease-in-out; }  #topbar a:hover { background-color: {color:top bar text hover bg}; color: {color:top bar text hover}; } 

css content:

.entry { position: relative; width: 500px; background-color: {color:entries}; border: 2px solid {color:entries border}; margin-bottom: -30px; margin-top: 55px; margin-left: 400px; padding: 10px; word-wrap: break-word; } 

and html both header , entries, right next each other:

<div id="topbar">...</div></div> <div class="entry">...</div></div> 

thank you!

comet! problem on custom pages, header child of .leftbg while on main page header peer of else. #topbar has z-index of 999, affects peers (in case, .entries). see this, inspect element #topbar on custom page , on home page. in html, header either placed other entries (so z-index:999 places header above other content) or child of .leftbg, has default z-index of "auto".

to fix this, add z-index:1; #leftbg. while change z-index of .entry -1, might break else i'm not super familiar tumblr's layout.

on note, i'd suggest disabling autoplay on musicplayer. it's not thing have autoplaying content when user might not expect play.