Georg, I knew you'd come through. The difficulty with your proposed fix (the max width setting) is that the desired limit to be placed on the width of images isn't 100%, it's 100%-200px, 200px being the width of the navigation panel.
I don't suppose that CSS has a way to say "100%-200px", does it? I am not going to worry about the finer points for IE6. The thing that distresses me about the intransigence of standards folks is that there are significant display behavior problems that are a given with a tableless layout that are very difficult to address, and every time I read an article or book touting some new layout, I wonder, whether the fab new layout has 'gotchas' laying in wait for me. The last couple of times I tried to re-do my site layouts table-less, I ran into this problem and others like it, got discouraged, and went back to using 1 table to contain the navigation / main body, and doing all the rest the 'right' way. I am close to considering it in this case, honestly, because having the content poke through the container is just not acceptable. It's easy for people to make fun of table based coding, and to go on about spacers and such, but the bottom line is that having the content panel not enclose the content or for it to render below the left navigation are both just not acceptable behaviors. If CSS could be persuaded to give me this very simple display behavior, I would have switched to table-less literally years ago. Sigh. Lori On Wed, Dec 3, 2008 at 2:25 PM, Gunlaug Sørtun <[EMAIL PROTECTED]> wrote: > Lori Brown wrote: > >> http://www.ertcorp.com/layoutTest/publications.php > >> 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 usually solve such cases by declaring 'max-width' on images - for your > case something like the following... > > html>body #main img {max-width: 100%; height: auto;} > > This will keep things somewhat under control in new browsers, but won't > do any good in older versions like IE6 - that's why I prevent it from > seeing the code. > > Browsers are generally not very good at scaling images, but with few, if > any, options left the result might be acceptable. > > One can of course hide the overflow in IE6 and older, but that's not > always a good solution and not easy to apply to your layout. > > > FWIW: the problem can be solved, but I don't think you'll like the > solution... > <http://www.gunlaug.no/tos/moa_10.html> > ...and neither do I for that matter :-) > It will also cripple IE8 and send it back to IE5.5 level CSS support. > > regards > Georg > -- > http://www.gunlaug.no > -- =========================== 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/
