>From what I can see in FF/Firebug the problem that's causing the side bar to
>push down is this:
#content {
margin: 0 280px 0 20px;
}
That's a huge margin on the right side of the content div. Plus there are no
width specified for either of the divs: #content & #primary. If you're not
going to specify a width you should at least float the content div left along w
the primary div float right as you have.
Elli Vizcaino
Helping artists, entrepreneurs and small
businesses knock the socks off the competition!
http://www.e7flux.com
----- Original Message -----
> From: Christian Kirchhoff <christian.kirchh...@editura.de>
> To: "css-d@lists.css-discuss.org" <css-d@lists.css-discuss.org>
> Cc:
> Sent: Wednesday, January 4, 2012 5:54 PM
> Subject: [css-d] Nesting problem in html code
>
> Hello,
>
> I am kindly asking for help hoping that a dozen pairs of eyes might see more
> than I do.
>
> A friend of mine has a Wordpress blog: http://run-united.com
>
> He told me that after he changed something, there was a problem in the start
> page: The right column containing certain widgets was suddenly pushed down
> below
> the main column with the recent article's teaser texts. Almost as if if
> suddenly had a "clear: " defined.
>
> One problem when analyzing is that browsers sometimes do some yutocorretion
> of
> html text, closing elements who's closing tags are missing etc.
>
> But here is what I found out: On the startpage the structure within the #main
> div is (viewed in Firefox/Firebug)
> <div id="container">
> <div id="content">
> </div>
> <div id="primary">
> </div>
> </div>
> <div id="footer">
> </div>
>
> However, if I look at the source code, I see a comment naxt to a closing
> </div> saying that this ends the #container, and AFTER that the
> div#primary begins.
>
> If I click on an article (e.g. http://run-united.com/?p=3452), the error
> doesn't occur on that page. And in Firebug I see that the div#pimary comes
> AFTER the div#container.
>
> Thus I guess the problem is that on the startpage somehow a tag is not
> properly
> closed or something like that, and Firefox and other browsers do some
> autocorrection that results in the div#primary being within the
> div#container.
> And that results in the css rules being executed in a wrong way and in the
> div#primary being pushed down.
>
> Has anybody had a similar problem and maybe knows the cause for this?
>
> My friend deleted the last article/post he added, but the error stayed. I
> looked
> at the the contents of both the last articles and the widgets within the
> admin
> panel of the Worpress blog, but I couldn't find any tags that weren't
> closed properly.
>
> I apologize if this is the wrong mailing list for such a problem. Just let me
> know and I won't bother any more. Otherwise any help would be appreciated.
>
> -- Best regards
>
> Christian
> ______________________________________________________________________
> css-discuss [css-d@lists.css-discuss.org]
> http://www.css-discuss.org/mailman/listinfo/css-d
> List wiki/FAQ -- http://css-discuss.incutio.com/
> List policies -- http://css-discuss.org/policies.html
> Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
>
______________________________________________________________________
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
