Hello everyone, I have a couple of problems and I’m pretty sure they’re something simple.
First off, on the working site in question, which has all been constructed inline, when I enlarge the text in the body copy section it overflows the outer white ‘page’ area. I’ve tried all settings on this holding div but nothing seems to work, so any suggestions welcome.
Secondly, on publishing, it says there’s an error with the CSS Menu action and I can’t work out why. At the moment the only link is back to itself on the Home page.
I had a look at the Clearfix action and saw a comment by someone saying that 99% of such cases can be solved by setting the outer dive to overflow: hidden. I went back and tried that before the Clearfix action and it worked! Any idea why?
Now just the css menu problem, but thanks again for pointing me in that direction.
Trev
On 24 Jul 2013, at 09:48, Thomas Kimmich wrote:
ohh - just a guess with no warranty:
Clearfixing (action available) the #Bodyholder could do the game (cause it contains floating items).
I had a look at the Clearfix action and saw a comment by someone saying that 99% of such cases can be solved by setting the outer dive to overflow: hidden.
… so this guy has unfortunately no idea what overflow means :-).
If you set overflow:hidden you disallow, as the word says, any overflowing content.
Examples?:
Drop Down menus are cut off as well as other overlapping divs within a box-in-box model.
So basically I would say that 1% can be fixed by overflow:hidden while 100% can be fixed by clearfix(ing).
Furthermore I anyway suspect a lil bug in Freeway, cause I had it in another page, that also inspectors setting was overflow:visible, the relating published css-property had been overflow:hidden. I ended up correcting this by extended DIV dialog.
I went back and tried that before the Clearfix action and it worked! Any idea why?
What worked? I can’t see anything working right now.
excellent. I think in your case here it’s pretty much OK to do the overflow:hidden, so no need for the action. Just keep in mind for other purposes that cut-off is exactly caused by this (and will be fixed by the action).
On the css-menu I’m unfortunately a few numbers too shorthanded - so sorry if I’m not of help here.
I had applied the CSS Menu action to the holding box and not the menu box!
(Slinks away into a quiet corner with a very red face)
All ok now.
Trev
On 24 Jul 2013, at 10:48, Thomas Kimmich wrote:
Hi Trev,
excellent. I think in your case here it’s pretty much OK to do the overflow:hidden, so no need for the action. Just keep in mind for other purposes that cut-off is exactly caused by this (and will be fixed by the action).
On the css-menu I’m unfortunately a few numbers too shorthanded - so sorry if I’m not of help here.
Just a quick note about overflow in the context of float-clearing. There are three basic ways to stop floated objects from “falling out” of their container: you can float the container, you can set the container to overflow: hidden, and you can add a small object to the end of the series of floated objects that is set to clear:both.
This last trick is what the Clearfix Action does.
The first two tricks cause the browser to calculate layout properties for the parent container; they are equally valid ways to accomplish the same goal, and they have the added benefit of not adding a non-semantic element to your layout.
The only time you would want to avoid the overflow:hidden trick is if you also need to pull a child element outside the bounds of the parent container using absolute positioning. And the “float to clear a float” trick causes a lot of added complexity in a centered layout, which is why it’s not the first thing to try in many cases.
Walter
On Jul 24, 2013, at 5:48 AM, “Thomas Kimmich” email@hidden wrote:
Hi Trev,
excellent. I think in your case here it’s pretty much OK to do the overflow:hidden, so no need for the action. Just keep in mind for other purposes that cut-off is exactly caused by this (and will be fixed by the action).
On the css-menu I’m unfortunately a few numbers too shorthanded - so sorry if I’m not of help here.
Just a quick note about overflow in the context of float-clearing. There are three basic ways to stop floated objects from “falling out” of their container: you can float the container, you can set the container to overflow: hidden, and you can add a small object to the end of the series of floated objects that is set to clear:both.
This last trick is what the Clearfix Action does.
The first two tricks cause the browser to calculate layout properties for the parent container; they are equally valid ways to accomplish the same goal, and they have the added benefit of not adding a non-semantic element to your layout.
The only time you would want to avoid the overflow:hidden trick is if you also need to pull a child element outside the bounds of the parent container using absolute positioning. And the “float to clear a float” trick causes a lot of added complexity in a centered layout, which is why it’s not the first thing to try in many cases.
Walter
On Jul 24, 2013, at 5:48 AM, “Thomas Kimmich” email@hidden wrote:
Hi Trev,
excellent. I think in your case here it’s pretty much OK to do the overflow:hidden, so no need for the action. Just keep in mind for other purposes that cut-off is exactly caused by this (and will be fixed by the action).
On the css-menu I’m unfortunately a few numbers too shorthanded - so sorry if I’m not of help here.