- From: Håkon Wium Lie <howcome@opera.com>
- Date: Fri, 11 Jul 2008 21:35:07 +0200
- To: fantasai <fantasai.lists@inkedblade.net>
- Cc: "www-style@w3.org" <www-style@w3.org>
Also sprach fantasai: > 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. Right. There are two types of triggers: page-break triggers and first-page triggers. The example doesn't trigger page-break (because the page names are the same), but it does trigger first-page. That is, the pages where div elements start will be considered first pages because they have non-auto values on the 'page' property. In practice, I expect styles like these to be used in combination with explicit page breaks. E.g.: <div style="page: chapter; page-break-before: left"/> <div style="page: chapter; page-break-before: left"/> However, we also have to deal with the situation where the second div element continues on an existing page. This could be problematic if because the page, most likely, already has been laid out and we do not want to change the size of the page area. We could address this in several ways, e.g. by saying that page-name:first will only have effect if the element starts on a new page. Or that the page area cannot be set unless the element starts on a new page. -h&kon Håkon Wium Lie CTO °þe®ª howcome@opera.com http://people.opera.com/howcome
Received on Friday, 11 July 2008 19:36:04 UTC