W3C home > Mailing lists > Public > www-style@w3.org > July 2008

Re: [css3-gcpm] [css3-page] Named page lists

From: fantasai <fantasai.lists@inkedblade.net>
Date: Fri, 11 Jul 2008 10:46:00 -0700
Message-ID: <48779C58.5000508@inkedblade.net>
To: Håkon Wium Lie <howcome@opera.com>
CC: "Refstrup, Jacob Grundtvig" <jacob.refstrup@hp.com>, "www-style@w3.org" <www-style@w3.org>

Håkon Wium Lie wrote:
> Also sprach Refstrup, Jacob Grundtvig:
> 
>  > Therefore when checking for <named-page>:first you'd have to go
>  > back to the nearest ancestor with a page valid other than 'auto'
>  > and match first iff the current page is the first page for that
>  > ancestor to appear.
> 
> I ran out of memory trying to parse that sentence :)
> 
> In my mind, which is arguably quite simple, it appears easier. Here's
> a pseudo-algorithm:
> 
>   n = element.page;
> 
>   if (n == auto) then p = ancestor.page; /* and so forth until a non-auto value, or the root element is found */
> 
>   if (n != name-of-the-current-page) then {
>      page-break();
>      create-new-page(n); 
>      name-of-the-current-page = n;
>   }
> 
> When a new page is created, all the rules set on that page --
> including left, right and first -- must be applied.
> 
> Does this make sense?

Yes, it makes sense. :) But it doesn't answer the question of
how to deal with

   <div style="page: foo"/>
   <div style="page: foo"/>

which currently don't trigger (n != name-of-the-current-page), vs.
your example of

   <div style="page: chapter"/>
   <div style="page: chapter"/>

which you you seem to want to trigger that condition.

~fantasai
Received on Friday, 11 July 2008 17:46:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:55:10 GMT