Click to See Complete Forum and Search --> : layout
JunkMale
05-06-2010, 01:11 AM
How do I get the content of a div to sit below another rather than to have them appear overlapped despite the float:right; setting for both DIV elements mean that they would...
The menu element in the same container sits as it should when the float:left; is set or not.
I have tried an empty div element with the clear:both; between the elements that overlap but it does not improve matters.
div's do that naturally without the float.
JunkMale
05-06-2010, 01:30 PM
The problem I am getting is that I have a div element and in it I have 2 further div elements, one is float left and the other is float right, they behave properly until I add a div element outside that group and find that the element outside is on top of the other elements.
The basic structure is this
<div id="head">
<div id="logo"></div>
</div>
<div id="search"></div>
<div id="contentwrapper">
<div id="menu"></div>
<div id="content"></div>
</div>
<div id="footer"></div>
The menu sits left, the content sits right but I find that the search box sits over the top of the content when it should be above it and not obscuring it.
the head element is a banner, the logo is a small 100x100 image, they behave properly.
The snip of the page showing the problem shows the problem and it is a case of the content div does not appear to be behaving, why it sits on the same line as the search div element is confusing because they are completely separate elements and the content div and menu should sit one line below the search, well put it this way, the "Menu" element does exactly that but the content does not.
JunkMale
05-08-2010, 04:05 AM
What is the css?
I got it sorted by using a position:relative; followed by a top:5px; setting and the thing sits correctly.
Urmmm, yes, the CSS... hack job that it is, would possibly provide many hours of amusement so its best to say its a complete mess I am working on it... I said to my friend that the his site was officially limping, it is viewable but nothing usable at present.
TBH I think it was more to do with the Komposer editor adding in lots of <br> tags that was the main issue, as soon as I went over to a plain text editor with highlighting to remove them, the page began to behave better.