|
|
Posted by dorayme on 12/30/07 21:31
In article
<doraymeRidThis-995037.10592529122007@news-vip.optusnet.com.au>,
dorayme <doraymeRidThis@optusnet.com.au> wrote:
> In article <slrnfnavhr.366.spamspam@bowser.marioworld>,
> Ben C <spamspam@spam.eggs> wrote:
>
> > > http://netweaver.com.au/floatHouse/
> >
> > One small inaccuracy or ambiguity there: you say 'there is a way to
> > force inline (and other) materials to clear the bottom of floats: via
> > the css instruction called "clear"'.
> >
> > Since CSS 2.1, you can only actually set clear on block-level things
> > (although I think in CSS 2 you could set it on inlines). Maybe by "via"
> > you meant the inlines go in another block-level element on which you've
> > set clear, which is what the examples show, but perhaps it's not, er,
> > clear.
> >
> > An exception is made for <br> which is display: inline and on which the
> > clear property does work in browsers. Although technically a violation
> > of CSS 2.1, it would be a bit strange to allow the HTML clear attribute
> > but not the CSS clear property so I think that's why they do it.
>
> Thanks. I was meaning the css clear on other block level
> elements. But perhaps I better make this clearer when I next take
> a look.
I took a look this morning and added bits. Thanks for this. I
also mentioned about the <br>. I did not go into why there was an
exception but thanks for reminding me about the probable reason.
[What a strange little thing a <br> is, a specialist inline
soldier that gives a peculiar final order: to make the path ahead
instantly disappear. What a responsibility! <g>]
--
dorayme
Navigation:
[Reply to this message]
|