SitePoint Sponsor

User Tag List

Results 1 to 12 of 12

Thread: Footer went all weird!!!

  1. #1
    SitePoint Evangelist
    Join Date
    Aug 2009
    Posts
    473
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Footer went all weird!!!

    Need some help, this was working perfectly but the I did something and cant remember what and it went all goofy on me, any ideas what I did.

    Heres the page...

    http://keatinginc.ca/commercial/asbe...tementtesting/

    Also, on other pages it looks ok but it doesnt have that image there so it may not be and seems to me that on other pages the footer should be down at the bottom but it isnt there a bit of room, any ideas what happened.

    Thanks,

    Mike

  2. #2
    SitePoint Evangelist
    Join Date
    Aug 2009
    Posts
    473
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Looks ok in Firefox but in Chrome and Safari looks all messed up, so could imagine IE. Im guessing Im missing a div or something but am confused on whats going on.

  3. #3
    SitePoint Enthusiast
    Join Date
    Mar 2011
    Posts
    70
    Mentioned
    2 Post(s)
    Tagged
    0 Thread(s)
    Found it in chrome and safari. In #footer {} line 380 remove the margin-top: -380px;

    In IE there is some other things going on though that will need to be addressed.

  4. #4
    SitePoint Evangelist
    Join Date
    Aug 2009
    Posts
    473
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Thanks Jeremy, but not really what I'm looking for as need the -380px on the margin-top as it is a sticky footer. I'm not too sure what went wrong at all cause it was working not too long ago.

  5. #5
    Life is not a malfunction gold trophysilver trophybronze trophy
    SitePoint Award Recipient TechnoBear's Avatar
    Join Date
    Jun 2011
    Location
    Argyll, Scotland
    Posts
    3,825
    Mentioned
    132 Post(s)
    Tagged
    5 Thread(s)
    Have you managed to fix it, because it looks the same here on Firefox and Chromium (on Linux) and I don't see any problems.
    If you're a bear made of mohair, ponder on the nature of a mo.

  6. #6
    SitePoint Evangelist
    Join Date
    Aug 2009
    Posts
    473
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Nope havent managed to fix it yet, still looks messed up on my Chrome and Safari but ok in Firefox

  7. #7
    SitePoint Enthusiast
    Join Date
    Mar 2011
    Posts
    70
    Mentioned
    2 Post(s)
    Tagged
    0 Thread(s)
    Sorry, that wasn't helpful. I didn't realize it was supposed to be sticky, and my small browser window didn't help.

    Anyways, I went through it with both firebug and and chrome dev tools. There are a lot of elements not properly clearing their containers, for instance, #main, .page-content, .page-wrapper, and the #sidebar are all shorter than their content. You may want to track down those issues and see if it straightens anything out.

  8. #8
    The CSS Clinic is open silver trophybronze trophy
    SitePoint Award Recipient Paul O'B's Avatar
    Join Date
    Jan 2003
    Location
    Hampshire UK
    Posts
    37,749
    Mentioned
    99 Post(s)
    Tagged
    3 Thread(s)
    Looks ok in chrome to me. What exactly is the problem?

    You do have some errors in your stylesheet here:

    Code:
    .instruc {
    	margin-left: 5px;
    	padding-left: 15px;
    	color: #F27A2D;
    	background: url(../images/nav-hover.png) no-repeat;
    }
    ​
    That stray character at the bottom!

    And a slash here at the end:

    Code:
    body:before {
    	content:"";
    	height:100%;
    	float:left;
    	width:0;
    	margin-top:-32767px;/
    }
    And as already mentioned above make sure your floats are contained.

  9. #9
    The CSS Clinic is open silver trophybronze trophy
    SitePoint Award Recipient Paul O'B's Avatar
    Join Date
    Jan 2003
    Location
    Hampshire UK
    Posts
    37,749
    Mentioned
    99 Post(s)
    Tagged
    3 Thread(s)
    Ok, I can see that this page is broken in chrome and thats because (as jeremyC already said) that you haven't contained the floats inside #main.

    I assume you need visible overflow so use this instead:

    Code:
    #main:after{
    	content:"."; 
     display:block; 
     height:0; 
     clear:both; 
     visibility:hidden;
    }
    #main{zoom:1.0}

  10. #10
    SitePoint Evangelist
    Join Date
    Aug 2009
    Posts
    473
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Perfect Paul!!!

    Thanks, works perfect now!!!

  11. #11
    Non-Member bronze trophy
    Join Date
    Nov 2009
    Location
    Keene, NH
    Posts
    3,760
    Mentioned
    23 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by Paul O'B View Post
    I assume you need visible overflow so use this instead:
    I'm wondering why you'd make that assumption, or send that mess of ugly CSS at it. Overflow+zoom, be done with it... doesn't appear to be anything that would require more.

    Though given the site is chock fully of accessibility and coding issues, I'm hardly shocked that I'm seeing four different BROKEN layouts in four different browsers here -- from the first line of code declaring it is in transition from 1997 to 1998, to the mess of bloated pointless javascript, to the massive space-wasting banner garbage on the home page, to the fix width layout with illegibly small px metric fonts, to the use of DIV for paragraphs, nonsensical heading orders, to the comment placements that could be tripping rendering bugs in IE and FF... It's a laundry list of "this is why you need to start over from scratch".

    Hardly a surprise for a turdpress template.

  12. #12
    The CSS Clinic is open silver trophybronze trophy
    SitePoint Award Recipient Paul O'B's Avatar
    Join Date
    Jan 2003
    Location
    Hampshire UK
    Posts
    37,749
    Mentioned
    99 Post(s)
    Tagged
    3 Thread(s)
    Quote Originally Posted by deathshadow60 View Post
    I'm wondering why you'd make that assumption, or send that mess of ugly CSS at it. Overflow+zoom, be done with it... doesn't appear to be anything that would require more.
    The author had this in the page:

    Code:
    #main {
        overflow: visible !important;
    }
    So I assumed there was a reason for it.

    But yes overflow:hidden would be my usual preference to the :after method.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •