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

[css-page-floats] First read-through

From: Alan Stearns <stearns@adobe.com>
Date: Thu, 26 Mar 2015 00:43:12 +0000
To: Johannes Wilm <johanneswilm@vivliostyle.com>, www-style list <www-style@w3.org>
CC: "public-ppl@w3.org" <public-ppl@w3.org>
Message-ID: <F5A7B065-BDA1-4547-82E6-4095617C051B@adobe.com>
Some notes as I read through the new draft:

It looks like the top level section 4 text needs an update to summarize both of the subsections and include values that have been added.

On float-reference:inline – can a line box be a block formatting context?

The example for a top 50% width float shows that it’s aligning both to the top and left of the column. If that’s the intended behavior, the left alignment should be included in the float:top description or in a more detailed description of how top/bottom floats are positioned (like the steps in 9.5.2 in CSS 2.2 [1]). Something like similarly to how a float:left must be placed as high as possible, a float:top must be placed as left (or inline-start) as possible.

I don’t understand the sentence that ends “so that the float behaves like an absolutely positioned element.”

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.

On deferring floats, I’d be interested in some text that says how this interacts with float stacking. If float stacking would already push a float’s position into the next column, does that count as satisfying float-defer:1?

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.

Thanks for the update!


[1] http://dev.w3.org/csswg/css2/visuren.html#float-position

Received on Thursday, 26 March 2015 00:43:43 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:52 UTC