Re: [css3-regions][css3-gcpm] Thoughts on Plan A and Plan B

On 2/17/12 7:53 AM, "Håkon Wium Lie" <howcome@opera.com> wrote:

> Stephen Zilles (and David Hyatt, with two indents) wrote:
> 
>>> From: David Hyatt [mailto:hyatt@apple.com]
> 
>>> (4) Problems with CSS Multi-column:
> 
>>>  Multi-column layout can't handle sourcing from multiple flows,
>>>  but is otherwise much better than regions for most use cases. In
>>>  this example:
> 
> Your image didn't make it to the archive [1]. I've uploaded a copy to [2].
> 
> [1] http://lists.w3.org/Archives/Public/www-style/2012Feb/0559.html
> [2] http://people.opera.com/howcome/2012/tests/magazine1.png
> 
>>> You have two flows. One of them is the main flow and goes across
>>> all three pages, but the "Sushi" sidebar flows from page one to
>>> page three. This is an example of where multi-column layout falls
>>> down because it can't express relationships like this.
> 
> This can quite easily be added if we allow selection of columns. For
> example, if the "sushi" flow is in the <aside> element, one could say
> somthing like:
> 
>   aside::region(2) {
>     float: page(3);
>   }
> 
> I've tried to write up code for the sushi page here:
> 
>   http://people.opera.com/howcome/2012/tests/magazine1.html
> 
> (It's a sketch, there are some unknowns in the equation. It'd be
> interesting to see what a similar sketch would look like using
> regions)

I don't understand the multicol solution for the 'sushi' flow. I'm
interpreting the layout intent as:

1. Start the sushi flow in a single region on page 1
2. Continue the sushi flow after all of the main article text is finished

The second (and possibly subsequent) regions for the sushi flow do not
necessarily land on page 3. Which page the sushi flow continues on depends
on how the main article text lays out. How this works is what we need to
define in some sort of 'page masters' module.

Thanks,

Alan

Received on Friday, 17 February 2012 16:13:08 UTC