Thanks all, Alan Gresley<a...@css-class.com> wrote: > Don, I think this may fix your layout but be warned, adding hasLayout may > cause other issues. > > *+html #content {height:1%;} /* fix for IE7 */ > * html #content {height:1%;} /* fix for IE6- */
This fix did not change solved the positioning problem between the sidebar area and the content area in IE7 (or IE5-6 but those not my high priority). This fix solve one problem putting #content where it belongs in IE5-6. Previously, it was stretched to the viewport. (using browsershots.org because I am on a MAC) Wow Alan. Sounds like you are writing a good CSS book. Any suggestions to modifying my approach here that will have fewer issues? In it's present state, I am just working to establish an optimum CSS layout for a blog/cms with a static sidebar and a fluid body, header, footer Philippe Wittenbergh<e...@l-c-n.com> wrote: > The parent of #content is a 'hasLayout' container (because of > overflow:hidden).... > Maybe choose another technique? Inserting an <hr> that clears the whole block > as last element in #container? That would even be semantic... I am all for trying out a different technique here. I am looking for the best approach possible for this blog/cms. This CSS will be a workhorse for a schools website. I am surprised how challenging a basic css layout still is cross-browser. But, it's what we have. David Laakso<da...@chelseacreekstudio.com> wrote: > 2/ Can the markup be changed? 3/ Does it really need to be that complex (bad > case of too many ids/classes)? My 'Ohlone' CSS layout template is a child-theme of a wordpress theme framework from themehybrid.com. That may explain some of the Markup complexity which can be changed/over-ridden in the child theme. So, I can simplify markup that way. ______________________________________________________________________ css-discuss [cs...@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/