dorayme wrote:
>
> I guess we have been through a few of these things earlier. I put up an
> example to strip all the things that I thought were not necessary to
> show the interesting thing you are raising but I don't think you are too
> impressed with this! I guess we think differently, I find it s to
> get rid of things I see as not relevant to the issue like wrappers to
> each pair of divs, which wrappers are not given any relevant css, widths
> that do not affect the basics and so on. This is not meant as some sort
> of invasion of your stuff, all I can do is say what I find clear and
> what not and hope you understand.

I didn't want the focus removed from my example initially since I had a
question still unanswered at the time as presented in my example. I am
not encumbered by some of the 'not relevant things' since they were
there to assist in visually presenting how I see things. I have no
problem with your examples as in:
<http://netweaver.com.au/alt/visibleOrder.html> which I think present
the same thing from a slightly different visual view.

> I am not keen on using any phrase printed by others (including the css
> specs) if it does not signify something to me in my understanding.
>
> I am inclined to actually use the phrase "containing block" where the
> context shows it to do a job of containing. Your containing blocks don't
> contain anything obvious (except their own text or pictures, a sense in
> which most elements are containers). You seem not to be referring to
> what you are calling wrappers.

In my examples, "wrapper" and "containing block" are two different things.
The "wrapper" is simply used to reposition the segment pairs. In your
examples in the link I mention above, you use headings to accomplish
this w/o wrappers.
The "containing block" is each one of the yellow boxes in every one of
your examples on the page linked above (yellow boxes in my examples as
well). It is a bit counter-intuitive in that normally a container comes
first in the markup, but in the case with floats, the "container block"
comes _after_ the float. The "container block" contains the float (which
is set to 0,0 of the container block) and line box(es) which are shifted
to the right of the float. It is perhaps also counter-intuitive because
it does not appear in the markup but is an auto-creation by the
appearance of a float - a special feature of the float.

I wanted to answer some more to other points below, but have run out of
time. Must do other things today. The meat is in the above anyway. I
like your examples.

--
Gus