Re: [css-page-floats] The 'clear' values are backwards

> On Jan 26, 2016, at 7:52 AM, Johannes Wilm <johanneswilm@gmail.com> wrote:
> 
> 
> 
>> On Tue, Jan 26, 2016 at 4:40 PM, Brad Kemper <brad.kemper@gmail.com> wrote:
>> 
>> 
>> > On Jan 25, 2016, at 5:05 PM, Johannes Wilm <johanneswilm@gmail.com> wrote:
>> >
>> > After a small conversation offlist: We seem to really have been in agreement. We meant the same thing, we just used different words for it.
>> >
>> > So the conclusion is:
>> >
>> > If we have three floats rights after oneanother where the first float is placed on page one. And the second float has the clear property set so that it will be placed on page two (and not page one), then also float three (which doesn't have the clear property set) will be placed on page 2 (or later if there is not enough space on page 2). Float three will therefore not be placed on page one, even though there would be enough space for it there. We will make sure that the wording ensures that. This is also what inline floats do, so pagefloats are no exceptions.
>> 
>> Wouldn't it be all subsequent content that would go to the next page? 'Clear: left' causes all subsequent content to clear the left float.
> 
> Not all subsequent content, but all subsequent top pagefloats (if one has cleared for top), right? All the surrounding non-float content will continue to be in that same line and not be moved further down when you clear.

It isn't really analogous to inline 'clear' as much then, and should maybe have a different name. Inline clear causes all subsequent content to move to the next line. I would expect the page float 'clear' to causes all subsequent content to move to the next page/fragmentainer. 

>> Would 'clear: top' set on a non-float also cause it to move to the top of the next page? Clear:left can be set on any element, not just those with float:left.
> 
> We need to think this through. With non-floats, we don't know what the float-reference is, so unless we come up with something we won't know whether we are clearing the column/page/region. 

Hmmm. 

> Also, see Shinyu's comment regarding this topic: https://lists.w3.org/Archives/Public/www-style/2016Jan/0190.html

That might be useful, but it seems more like something that is clearing block floats (things that float to the top of the block, instead of the top of the fragmentainer). 

>> Is this the same as break-before:always?
> 
> 
> I don't think it is. Only the float and all following floats are moving to the next page/column, not the surrounding non-float content.

Yeah, that clearing of fragmentainers is pretty different from how inline 'clear' clears line boxes.