Dear CSS-discuss: I have a draft site here: http://www.ertcorp.com/layoutTest/publications.php
It validates as html 4.01 strict and is written in a table-less 2 column layout using some styles from Dan Cederholm & the guy at Berea st. I am starting to fill this draft 'container' with some specific content to test its behavior and appearance, and I have discovered something very bothersome, and I am trying to understand whether this behavior can be addressed in a standards-based css solution. Look at the page referenced above with the very wide map image in it. Adjust the width of your browser window to be narrower than the width of the nav + the image. The image sticks out of the side of the enclosing box. Ugh! This is not ok, to me, and would probably not be well-received by my users. I tried applying "display: table-cell;" to the div class 'mainInner'. This change kept the image enclosed by the design as desired, but when the browser window is narrowed, 'mainInner' drops down below the navigation, which is not good either. The appearance / behavior I am trying to achieve is what you'd get if you used.... a freakin' table. (pause to clear away rotten vegetables just thrown at me by standardistas) I want the mainInner div to sit NEXT TO the navigation panel no matter what the users do with the width of the browser window. If the browser window gets too narrow, just give me a scroll bar, do not shift mainInner down the page. And I want whatever gets put inside mainInner to stay inside of mainInner without exception. Can this be achieved? Am I going to have to rewrite the entire structure of this page to use a fixed position for the mainInner div? Suggestions for resources for a good no-gotchas fix? If I were only designing this page layout for my own use, I would be able to manage the problem by managing the size of fixed width content elements placed in it. But this layout is going to be used by a number of client site content managers who I will assist in building their pages, but who are not going to be strong on addressing fussy authoring details. So I'm trying to solve likely problems before handing them over to the users. Any assistance is appreciated. Lori -- =========================== Lori Brown web developer & troublemaker If the automobile had followed the same development cycle as the computer, a Rolls-Royce would today cost $100, get a million miles per gallon, and explode once a year, killing everyone inside. ______________________________________________________________________ css-discuss [EMAIL PROTECTED] 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/