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: Tue, 08 Jul 2008 09:00:30 -0700
Message-ID: <48738F1E.9040409@inkedblade.net>
To: Håkon Wium Lie <howcome@opera.com>
CC: www-style@w3.org

Håkon Wium Lie wrote:
> Also sprach fantasai:
> 
>  > I'm trying to prepare CSS3 Paged Media for Last Call.. so it would
>  > be good to know if we need to make 'page' not inherit or anything
>  > like that.
> 
> I support the idea of changing 'page' from being inherited to not
> being inherited. If we do so, we can probably address the issue that
> the named page lists in GCPM is (unsuccessfully) trying to address;
> setting a different style on the first page in a series of pages. For
> example, the chapter title is often printed on the first page of the
> chapter and the chapter title should therefore not be printed in the
> running header of that first page. One could then write:
> 
>   div.chapter { page: chapter }
>   h2 { string-set: title content() }
>   @page chapter:left { @top-left { content: string(title) }}
>   @page chapter:first { @top-left { content: none }}
> 
> This code feels right to me, but it wouldn't work as long as 'page' is
> inherited (because 'chapter:first' in practice would match all pages).

It looks very elegant, but it's not backwards compatible. :(
:first right now is defined to only apply to the first page of the
document.

~fantasai
Received on Tuesday, 8 July 2008 16:03:29 GMT

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