Re: [css-page-floats] ED 20130912

Hello Tony, 

 > 1, Do page floats break?  What happens when, e.g., a page float contains a
 > table that is longer than the page?

The Page Floats specification doesn't say anything about the breaking
behavior, so page floats break like other elements/floats. It
certainly makes sense to break tables that are longer than the page.

 > 2. 'clear' allows 'top' or 'bottom', but there are times, e.g., in a
 > scientific journal article, when you want 'float: top', don't want
 > graphics, etc., to be stacked, but would prefer the second graphic to
 > float to the bottom of the same page rather than pushing the second
 > graphic to the next page and further away from its reference.  If there's
 > enough graphics or tables in the article, at one per page, the graphics
 > and tables will end up past the start of the 'References' sections, which
 > is usually seen as a bad thing.  How would that be done?

So, you're saying that you would prefer a top-floating figure, but if
another page float has taken that position, the figure should go to
the bottom rather than being pushed to the next column/page?

That's a good use case, I think -- often you don't care if the element
is top or bottom, it should just be alone (or, at least, be first in
that position).

How about:

  .figure {
     float: top;
     clear: alone;

Or maybe:

  .figure {
     float: top;
     clear: first;

I don't think we need to distigush between pages and columns -- the
goal is to be closest to the reference point.

              Håkon Wium Lie                          CTO °þe®ª        

Received on Tuesday, 17 September 2013 09:58:19 UTC