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

Re: [gcpm] custom pages and page lists

From: MURAKAMI Shinyu <murakami@antenna.co.jp>
Date: Wed, 20 Aug 2008 14:42:59 +0900
To: "Grant, Melinda" <melinda.grant@hp.com>
Cc: Håkon Wium Lie <howcome@opera.com>, "www-style@w3.org" <www-style@w3.org>
Message-Id: <20080820135408.91ED.C598BCD7@antenna.co.jp>

"Grant, Melinda" <melinda.grant@hp.com> wrote on 2008/08/20 12:10:19
> 
> Hello Murakami-san,
> 
> You said, in http://www.w3.org/2002/02/mid/20080819154137.91C3.C598BCD7@antenna.co.jp;list=www-style, wrt Option D (use ':first'):
> > UC3.1:
> > Not possible.
> >
> >     table { page: rotated }
> >     <table>...</table>
> >     <table>...</table>
> >
> > These two tables are rendered on separate pages.
> 
> I would think the tables should be on the same page if they fit, because the 'page' property for the two is the same, and there is no 'table :first' page context.  Why do you think they must be on separate pages in this case?


  OPTION D

  UC1:

    @page chapter { 
      @top-center { content: string(title) }
    }
    @page chapter:first { 
      @top-center { content: none }
    }
    div.chapter { page: chapter }
    h1 { string-set: title content() }

The div.chapter must start new page.
I assumed Option D has the following assumption same as Option C:

   - every element with a non-auto value on 'page' start on a new page,
     so there would e.g. be a page break between these two div elements:

       div.chapter { page: chapter }
       <div class="chapter">...</div>
       <div class="chapter">...</div>

UC3.1's tables are same case with this div.chapter.

-- 
Shinyu Murakami
http://www.antennahouse.com
http://www.antenna.co.jp/AHF/
Received on Wednesday, 20 August 2008 05:43:48 GMT

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