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

On 2/24/12 9:05 AM, "Brad Kemper" <brad.kemper@gmail.com> wrote:

> '@slot' without any name means "page content region" (with no 'flow-from', as
> it just receives normal, mundane, non-css3-regions flow), and cannot be styled
> directly. Instead, it can contain selectors for styling normal content that
> appears on that page. So the example would look like this:
> 
>  @page fishy {
>     @slot(sushi) {
>        position: absolute;
>        top: 0; bottom: 0;
>        right: 0; width: 10em;
>     }
>     @slot { 
>        article { 
>            margin-right: 11em;
>            /* meaning, on this page template,  */
>            /* add a right margin to this element */
>     }
>  }
>  @page { /* default for page 2 */ }
>  aside { flow-to: sushi }
>  article { /* no flow-to, so goes to all pages as normal */ }
> 
> I suppose we might also need a special property for use within @page that
> means "don't accept normal flow on this page, and only accept region flow
> instead".

In terms of using names to associate content with slots, we already have
named flow idents from css3-regions to use. So your slot-content-assignment
syntax could change to something like this (I'm adding an element property
to associate the article element(s) with one or more paginated templates)

 @page fishy {
   @slot {
     /* positioning */
     flow-from: sushi;
   }
   @slot {
     /* positioning */
     /* no content or flow-from declaration, so use normal flow */
   }
 }
 aside { flow-into: sushi; }
 article { master-template: fishy; }

If a slot has no content assigned to it with the 'content' or 'flow-from'
properties, then it defaults to normal flow. You can create a paginated
template that does not accept normal flow by making sure that each slot has
assigned content.

Thanks,

Alan

Received on Friday, 24 February 2012 21:40:08 UTC