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

Also sprach James Elmore:

 > It is, of course, possible to place something at the end of a div/ 
 > chapter/section using the ::after mechanism. It is equally possible  
 > to place elements/decorations/text/generated content at the start of  
 > a section with ::before. Since this is true, does that reduce the use  
 > case for :first page?

The use cases for the :first page is primarily to remove
headers/footer on the first page of a chapter -- it's common to print
the chapter title in running headers/footers, except on the first page
of a chapter.

This use case cannot be handled by ::before.

 > > It's slightly harder to implement :last than :first, because the
 > > formatter doesn't necessarily know that a page is the last until it
 > > has been formatted. Loops may occur.
 > 
 > I remember implementing loops where something which went first had to  
 > be handled and also ones where something had to be guaranteed to be  
 > last, the :last ones were usually harder. When possible, I recoded  
 > the loops to be left-associative rather than right, which simplified  
 > things. [If I'm not being clear about left- and right- associations,  
 > let me give one short example. A list of comma separated items can be  
 > coded as {item ,}* {item} or as {item} {, item}* The first example  
 > grows to the left and the second grows to the right.]

Interesting.

 > Loops may also occur -- as you mentioned before -- where the element  
 > will not fit in the space remaining on the page, which creates a new  
 > page.

Right.

 > Now, will there be two of the elements?

I'm not sure I understand the question. An element which is split over
two pages is still only one element, but it is formatted into several
boxes.

-h&kon
              Håkon Wium Lie                          CTO °þe®ª
howcome@opera.com                  http://people.opera.com/howcome

Received on Saturday, 12 July 2008 22:25:05 UTC