shim
12-07-2004, 12:44 AM
I'm redesigning my site Import Rival (www.importrival.com). I am using the Ruthsarian/Skidoo (http://webhost.bridgew.edu/etribou/layouts/skidoo/) 3 column fluid layout.
When I view through Netscape 6, the columns are fine.
When I view through Internet Explorer 5, all columns are fine, as long as I use TEXT in them.
However, when I use the photolog(weblog) tag in the 3rd column, instead of using text, the 2nd column content get pushed down (http://www.importrival.com/skidoo.php).
I'm not getting any error messages regarding this when I turn the debug on.
Although the author of the template says that the code will not validate, I've also tried to eliminate the errors I've made.
Is it possible for the pics to be too large for IE without appearing visually so?
This is from a post I found by the Ruthsarian author:
> Any particular reason why box model hacks are used so much? Is it just
> preference?
>
> Usually what I do to get around IE's box model problems is doubling up
> key blocks. Example:
>
> <div id="masthead">
> <div class="inside">
> ... content ...
> </div>
> </div>
>
> with CSS looking like this:
>
> #masthead { width: 740px; }
> #masthead .inside { padding: 1em; }
>
> The idea is that the outer block has the width you want and any padding
> you need on the element is provided by the inside element. This is what
> I use in my layouts, which you can see at
> http://webhost.bridgew.edu/etribou/layouts/.
>
> The really big advantage here is the use of fewer hacks (if any) in your
> layout. That means less chance of some of the more obscure or newer,
> future browsers from being caught up in the hacks and destroying the
> layout.
>
> The disadvantage is the redundant markup. But if you approach the layout
> the right way, it might not have to be so redundant.
What am I missing?
When I view through Netscape 6, the columns are fine.
When I view through Internet Explorer 5, all columns are fine, as long as I use TEXT in them.
However, when I use the photolog(weblog) tag in the 3rd column, instead of using text, the 2nd column content get pushed down (http://www.importrival.com/skidoo.php).
I'm not getting any error messages regarding this when I turn the debug on.
Although the author of the template says that the code will not validate, I've also tried to eliminate the errors I've made.
Is it possible for the pics to be too large for IE without appearing visually so?
This is from a post I found by the Ruthsarian author:
> Any particular reason why box model hacks are used so much? Is it just
> preference?
>
> Usually what I do to get around IE's box model problems is doubling up
> key blocks. Example:
>
> <div id="masthead">
> <div class="inside">
> ... content ...
> </div>
> </div>
>
> with CSS looking like this:
>
> #masthead { width: 740px; }
> #masthead .inside { padding: 1em; }
>
> The idea is that the outer block has the width you want and any padding
> you need on the element is provided by the inside element. This is what
> I use in my layouts, which you can see at
> http://webhost.bridgew.edu/etribou/layouts/.
>
> The really big advantage here is the use of fewer hacks (if any) in your
> layout. That means less chance of some of the more obscure or newer,
> future browsers from being caught up in the hacks and destroying the
> layout.
>
> The disadvantage is the redundant markup. But if you approach the layout
> the right way, it might not have to be so redundant.
What am I missing?