A screen shot of what you think it is *supposed* to look like would be helpful for those of us using Safari.
As far as I can tell, your link looks exactly the same to me in Safari (2.0.4), Firefox (1.0.5.6) and Camino (1.0.1) on a Mac.
-------
Oh - oops. I guess I see now after having been to some of the other pages. The trees aren't stuck to the bottom on the index page? And the 1px jog. Okay. I get it. Sorry to be hasty replying.
From: Kansas City, MO , USA Insane since: Feb 2002
posted 09-16-2006 03:01
quote: reisio said:
I don't see the particular problem in the first screenshot.Y'know you can just make that stuff always at the bottom if you want, right?
i know there is, but i have yet to come accross a compliant crossbrowser solution... and i cant have a "fixed" footer, because then the tree is behind the text and looks like crap
quote: Steve said:
Oh - oops. I guess I see now after having been to some of the other pages. The trees aren't stuck to the bottom on the index page? And the 1px jog. Okay. I get it. Sorry to be hasty replying
i know there is, but i have yet to come accross a compliant crossbrowser solution... and i cant have a "fixed" footer, because then the tree is behind the text and looks like crapquote
What browsers do you need it to work in? (include versions)
I still don't see an issue with the first screenshot, btw. Don't have Mac OS setup atm so can't help with the 2nd yet.
If I understand correctly, it has to do with the white center content div extending below the hills/trees graphic. The index page does that in all three of the Mac browsers I mentioned, but on all the other pages of the site the trees are flush with the bottom of the content column (and the viewport for that matter). I don't know what's up with that 1px "jog" either, but that's gone on the other pages as well. I presume it has to do with the index page having no content (or insufficient content) in the content divbut haven't had time to investigate what that might have to do with anything.
Ensellitis: have you tried putting some content in that index page to see if it fixes itself?
Ah. So it's not just a "Mac thing", because I had the same disconnect at first. The screen shot looks more or less identical to what I saw on the index page. Once I went into some of the other pages (portfolio for example) and saw the hills/trees stuck to the bottom of the viewport I realized that was probably what the home page was supposed to look like as well.
I've been following this thread from the peanut gallery, and I have to say I am still a bit confused. My first thought would be what reisio mentioned, just fixing the footer to the bottom. But then you said this:
quote: Ensellitis said:
i know there is, but i have yet to come accross a compliant crossbrowser solution... and i cant have a "fixed" footer, because then the tree is behind the text and looks like crap
First of all, simply using "bottom:0" in your CSS declaration will work, and it is completely cross-browser. Secondly, I don't understand what the second sentence means: "the tree is behind the text and looks like crap"?
Maybe I'm just being dense, but I'm finding it hard to wrap my head around the problem here.
Oh, and it's nice to see you around here again. You too, Steve.
From: Kansas City, MO , USA Insane since: Feb 2002
posted 09-18-2006 18:18
well steve, your example screen there are it... i have pretty much decided that until i have enough text to push it down enough for all resolutions, i'm not going to do a "public release".
i added some seperators for single posts to help push everything down a little more.
suho, sorry i was so confusing... i have been like that for the last few months good to be back again... seems like no matter what, i keep coming back here...
anyways, the newest version, skinned to wordpress, can be found here. keep in mind i am constantly working on it, so if you see red borders around elements (thats what i do when testing padding/margins/ect) they arent there by accident :P