|
![](/i/fill.gif) |
>>> .h1 {margin-bottom:0}
>>
>> Wouldn't that mean that the margin between the header and the real
>> content would now be incorrect?
>
> Should still conform to line-height
> <snip>
I didn't think inline elements could have margins?
>> Not sure you need to use ".indent"; why not just "li ul" or something?
>
> Because the first ul isn't indented and it allows you to create an extra
> indent for a third level if needed without messing with child indicators
> that IE doesn't understand.
Ah. So the answer to "why not use child selectors" is simply "IE doesn't
understand child selectors"? Oh I *so* don't give a damn. :-P
>> Anyway, absolute positioning seems to work fine, but for the minor
>> detail that I need to figure out how wide the columns are supposed to
>> be...
>
> I try to avoid absolute positioning when possible, just because it takes
> things out of the flow. if I have to use it I ensure it's well-wrapped,
> but even then there can be some glitches where the positioning relates
> to the first parent that specifies a position rather than its container.
Yeah, it looks like styling this correctly is going to be fun... Still,
at this point, I'm still getting the page content to be generated
correctly. Assuming I tag enough stuff, it should be possible to fiddle
with the CSS later.
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
![](/i/fill.gif) |