W3C home > Mailing lists > Public > www-style@w3.org > April 2015

Re: [css-page-floats] First read-through

From: Johannes Wilm <johanneswilm@vivliostyle.com>
Date: Wed, 8 Apr 2015 13:13:52 +0200
Message-ID: <CABkgm-QWPufVBix7hArCkaHWuUKT9YkHjqYJHj=EyUa-X49WdQ@mail.gmail.com>
To: Alan Stearns <stearns@adobe.com>
Cc: www-style list <www-style@w3.org>, "public-ppl@w3.org" <public-ppl@w3.org>
On Thu, Mar 26, 2015 at 1:43 AM, Alan Stearns <stearns@adobe.com> wrote:

>   Some notes as I read through the new draft:
>

I have tried to incorporate most of this [1].

[...]

> I don't understand the sentence that ends "so that the float behaves like
> an absolutely positioned element."
>

Sorry, that was confusing. The point was that

>
>  I'd add an issue to section 5 noting that there needs to be much more
> added here, including how top/bottom and left/right floats interact, and
> how floats with different float references interact.
>

I added a note. You mean notes on how exactly the placement is determined
of line-start/end floats that are have a float-reference other than inline?


>
>  On deferring floats, I'd be interested in some text that says how this
> interacts with float stacking.
>

I have tried to add something simple [2].


> If float stacking would already push a float's position into the next
> column, does that count as satisfying float-defer:1?
>

I am not sure I follow. The idea is that floats first will be associated
with a particular fragmentation based on either the placement of the float
reference or, if specified, by float-defer. The placement of the individual
floats within a chain of fragmentations will happen from start to end. If a
fragmentation is overly full, any float that could not be placed will be
defereed to the next fragmentation.

I realize that the placement of floats and determination whether or not a
particular float will have to be deferred to a subsequent fragmentation
will need a clear description. But I am a little confused as what you feel
is needed to describe the connection between float deferrence due to
insufficient space and manual float deferrence via CSS rules.


>
>  Section 8 do you mean wrap-flow? I'm not sure that wrapping around both
> sides of a float (presumably with a float-offset) is a good idea.
>


Yes, the idea was here to make it possible to flow text on both sides of a
float. But maybe there is a different way to achieve the same in a better
way?

[1] http://dev.w3.org/csswg/css-page-floats/
[2] http://dev.w3.org/csswg/css-page-floats/#deferring_floats


Thanks for the feedback! I will be lookign at Florian's comments next.
Received on Wednesday, 8 April 2015 11:14:26 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:30 UTC