Re: [css3-regions] writing mode and directionality for flows

Hi Alex,

On 8/14/11 12:09 PM, "Alex Mogilevsky" <> wrote:

>A very limited set of properties on the region element affect content
>(other than region styling). Currently only column properties are
>candidates for that. And size of course.
>Considering that in paged media first page is the ICB, first region will
>be ICB too (right?),

Yes. This would align the regions behavior with that of pages
(, where the spec. says:

"The edges of the page area on the first page establish the rectangle that
is the initial containing block
<> of the

So it seems consistent to have that behavior for regions too.

>then it would be reasonable to expect that root writing mode is that of
>the first region element.

Sounds good to me too.

>BTW, what use cases depend on that? The only one I can think of is how
>many pages to skip for "break-after:even". Anything else?

This is something David responded to in a follow up email.

>-----Original Message-----
>From: [] On
>Behalf Of David Hyatt
>Sent: Thursday, August 11, 2011 9:43 AM
>To: Vincent Hardy
>Cc: CSS
>Subject: Re: [css3-regions] writing mode and directionality for flows
>On Aug 11, 2011, at 11:31 AM, Vincent Hardy wrote:
>> Hi Davd,
>> On 8/11/11 9:25 AM, "David Hyatt" <> wrote:
>>> What are the initial writing mode and directionality of flows? Can
>>> individual regions specify different writing-modes and
>>> directionality, thus causing how you paginate to vary from region to
>>> region in the same flow? I'm really hoping the answer is "No", and
>>> that - as with printing and multi-column elements - there is a single
>>> master writing mode and directionality that determines all of the
>> Yes, that is what it would be. In the new draft that is in the works,
>> the model is sticking to be very close (as much as possible and makes
>> sense) to pagination and multi-column.
>>> My suggestion would be to use the writing-mode and directionality of
>>> the first region to establish the pagination direction and to just
>>> ignore the writing-mode/directionality set on subsequent regions.
>>> Another idea would be to simply use the ICB's writing-mode and
>> This is missing from the spec. currently, I'll add an action item to
>> add something about the writing-mode direction.
>A third idea would be to support styling a pseudo-element for the named
>::flow(myflow) { writing-mode: vertical-rl; }
>Probably a bit silly to create a pseudo-element just to style the
>writing-mode / direction though. I kind of like the "use the first
>region" heuristic, but I'm curious what others think.

Received on Tuesday, 16 August 2011 18:45:32 UTC