Del Wegener wrote:
>>> http://www.edi-cp.com/newweb/products_ul_intro.php
> Thanks Georg. I decided that I really did want spans and not divs. I
> made the changes you suggested and of course everything worked
> perfectly! I then tried to find out what your css changes were all
> about. After much searching and reading I think I understand what
> they accomplish but I have no earthly idea of why they are needed.
> Nor do I see any way of figuring out what to do the next time.
>
> Some folks seem to advise using overflow-x:hidden all the time on
> "columns". Why? Why did you show that to IE 6 and & only?
IE6 expanded the width of that element initially - on your original, and
'overflow-x:hidden' is the quickest way to prevent such buggy expansion.
And, NO, one should NEVER add such restrictions unless there are real
problems and no better ways to fix them. "Overstyling" with all kinds of
"fixes" doesn't make IE6 any better, only buggier and more difficult to
control.
> I am pretty sure that * html div#container is seen only by IE6
> whereas *+html ... is seen only by IE7. Statements of the form /*
> IE6 */ are strictly comments to enhance readability by us mere
> mortals.
Correct (I don't need those comments ;-) ).
> Why on earth should I suspect that I need * html h1 { float:left;
> margin: 1em; 0;} ?
Apart from IE being made "on earth": no particular reason other than
that old IE is buggy. That's why we Norwegians have declared war on the
worst version (IE6)...
<http://blog.wired.com/business/2009/02/norwegian-websi.html>
...and hope to reduce its numbers to a level where we web designers can
more or less ignore its existence - at least in our part of the world.
> Do I need such a hack everytime I use H1, H2, or any of the other
> head tags?
Nope. It depends on their relations to other elements and their styles,
when subjected to IE bugs.
In your case the h1 was "wedged" in between two of the right-floats and
prevented the paragraphs from flowing up - as old IE saw it, so I
decided to float the headline out of there so it could rise to the top.
> Where can I read more about this stuff?
You'll find some in these places...
<http://www.brunildo.org/test/index.html>
<http://www.positioniseverything.net/explorer.html>
<http://www.howtocreate.co.uk/wrongWithIE/>
<http://www.gunlaug.no/contents/wd_1_02_03.html>
...but the only way to get a real understanding of these things, is to
create loads of tough test cases - as "real world" like as you can make
them - and run these cases across browser-land. Then browsers will
expose their weaknesses and bugs, and you can test out which fixes that
work and which doesn't. Nothing beats experience.
regards
Georg
PS: David Laakso pointed out [off-list] that your page, and my example,
looks a bit broken on really wide browser windows - the right-floats
part ends up looking weird since most floats expand in width while the
topmost with the image doesn't.
A 'max-width' of 1200 to 1400px added on #container would pretty much
solve that.
--
http://www.gunlaug.no
______________________________________________________________________
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/
