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

Re: [css-page-floats][css-overflow] First cleanup

From: Florian Rivoal <florian@rivoal.net>
Date: Thu, 26 Mar 2015 11:22:46 +0100
Cc: www-style list <www-style@w3.org>, public-ppl@w3.org
Message-Id: <4320F328-1845-463A-A9D3-DDE2ACD04A63@rivoal.net>
To: Johannes Wilm <johanneswilm@vivliostyle.com>

> On 26 Mar 2015, at 00:48, Johannes Wilm <johanneswilm@vivliostyle.com> wrote:
> 
> Hey,
> I have spent the last few weeks looking at the manuals of PrinceXML, the Antennahouse Formatter, Håkon Wium Lie's CSS Figure Spec [1] and have discussed with the Vivliostyle team what they would need from a page float spec. 

A few quick comments:

1) in the definition of the float and clear properties (especially for the ''left'' and ''right'' values), you should be able to use the terms ''line-left'' and ''line-right'', as defined in writing modes, to make things clearer.

2) float-defer is described in terms of "column/region/page". It probably should be defined in terms of fragmentation containers, which would also make it work using ''continue:fragments'' [1] (aka overflow:fragments, aka break-target:clone...)

3) Similarly, float-reference should probably get a value that let's you target the fragment boxes created by continue:fragments. Or a value (''any''?), that targets the closest fragmentation container ancestor you have, regardless of what kind of fragmentation container it is. Or maybe both.

- Florian

[1]http://dev.w3.org/csswg/css-overflow-3/#fragment-overflow
Received on Thursday, 26 March 2015 10:23:10 UTC

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