W3C home > Mailing lists > Public > www-style@w3.org > December 2016

Re: [css3-break] Transforms, Positioning, and Pagination

From: fantasai <fantasai.lists@inkedblade.net>
Date: Fri, 30 Dec 2016 18:33:20 +0330
To: Andrei Bucur <abucur@adobe.com>
Cc: "www-style@w3.org" <www-style@w3.org>
Message-ID: <06f1ff65-e749-af56-49b9-0cf029f19bad@inkedblade.net>
On 01/10/2013 06:56 PM, Andrei Bucur wrote:
> Hi fantasai,
>
> I have some questions about this new text in the fragmentation spec.

Hi Andrei,
Sorry for the extremely late reply, I lost track of this thread for a couple years.

> On Dec 1, 2012, at 12:37 AM, fantasai <fantasai.lists@inkedblade.net> wrote:
>
>> I had an action item to draft text for the resolutions from TPAC here:
>>   http://www.w3.org/mid/50A33BC0.9050903@inkedblade.net
>>
>> Here's the proposed text, with annotations:
>>
>>   | Fragmentation interacts with layout, and thus occurs <em>before</em>
>>   | relative positioning [[!CSS21]], transforms [[!CSS3-TRANSFORMS]],
>>   | and any other graphical effects.
>>
>> [This takes care of the resolution on relpos and transforms.]
>>
>>   | However, the separation and transfer of page boxes SHOULD occur last;
>>   | thus a transformed fragment that spans pages SHOULD
>>   | be sliced at the page breaks and print in its entirety
>>   | rather than being clipped by its originating page.
>
> 1. This second part refers strictly to pagination, not other fragmentation specifications such as multi-column or regions, right?

Yes.

>> [This is new; I suspect it's necessary to print many pages without dataloss.
>> I am unsure whether anybody implements it, however.]
>>
>>   | Absolute positioning affects layout and thus interacts with
>>   | fragmentation. Both the coordinate system and absolutely-
>>   | positioned boxes belonging to a containing block fragment
>>   | across pages in the same fragmentation flow as the containing
>>   | block.
>
> 2. Small nit: If this is to be applied general across the fragmentation specs, I think using words like "pages" should be avoided.

Good catch.

> 3. Do we have a text that covers what should happen with the CSS transforms coordinate systems when dealing with fragmentation? Maybe it would be worth mentioning each fragment gets its own coordinate system (so rotating a box with two fragments around its centre would rotate each fragment around its own centre).


I believe this is covered by

   | Fragmentation interacts with layout, and thus occurs <em>before</em>
   | relative positioning [[!CSS21]], transforms [[!CSS3-TRANSFORMS]],
   | and any other graphical effects.
   | Such effects are applied per fragment:
   | for example, rotation applied to a fragmented box
   | will calculate a rotation origin for each fragment
   | and independently rotate that fragment around its origin.

~fantasai
Received on Saturday, 31 December 2016 12:00:05 UTC

This archive was generated by hypermail 2.3.1 : Saturday, 31 December 2016 12:00:08 UTC