RE: [page][gcpm] should a named page start on a new page?

I was reading through part of gcpm and found the following conflict:-

21. Another change is that a single named page will result in a page break both before and after the element (in CSS 2.0 the page break after the element was conditional on subsequent 'page' values).

21.1 (under one or more named pages optionally follow by auto)

A page break is generated before the element unless the first named page in the list is the same as the current page.

Based on the examples given in 21.1 I would say the latter is correct and what we wanted.

- Jacob

> -----Original Message-----
> From: www-style-request@w3.org
> [mailto:www-style-request@w3.org] On Behalf Of Håkon Wium Lie
> Sent: Tuesday, September 16, 2008 3:24 PM
> To: fantasai
> Cc: Håkon Wium Lie; Grant, Melinda; www-style@w3.org
> Subject: Re: [page][gcpm] should a named page start on a new page?
>
>
> Also sprach fantasai:
>
>  > > I understand your resistance. I think there are two
> simpler option  > > that preserves the behavior from CSS2:
>  > >
>  > > 1) We can say that foo:first doesn't create a page
> break, but if there  > > is an explicit page break there
> already, foo:first will apply.
>
>  > I have a preference for #1.
>
> I've edited GCPM to reflect this behavior:
>
>   http://dev.w3.org/csswg/css3-gcpm/Overview.html#page-lists
>
> It seems, however, that the description of :first should go here?:
>
>   http://dev.w3.org/csswg/css3-page/#left-right-first
>
> -h&kon
>               Håkon Wium Lie                          CTO °þe®ª
> howcome@opera.com                  http://people.opera.com/howcome
>
>

Received on Wednesday, 17 September 2008 17:21:57 UTC