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

RE: [gcpm] border-parts

From: Grant, Melinda <melinda.grant@hp.com>
Date: Wed, 5 Nov 2008 21:02:19 +0000
To: Håkon Wium Lie <howcome@opera.com>
CC: "www-style@w3.org" <www-style@w3.org>
Message-ID: <763AE400FE923441B74861D534DF254955B16E98AA@GVW0433EXB.americas.hpqcorp.net>


Håkon said:
> How about:
>
>   page()
>
>     The element is floated to a named page, which is created for the
>     purpose of showing the element. The new named page should appear
>     as early as possible while still honoring the 'next' keyword.

I agree the preferred behavior should be to present it as early in the page stream as possible.  We may find more reasons that it must be delayed, so I would lose the 'while' clause as superfluous. Also if we're going to allow multiple items to flow to the same named page, it won't be new anymore.  And the element may not all resolve to a single page sheet.  How about:

        The element is floated to one or more page sheets styled according to the named page, which are created
        for the purpose of showing the element. Such floated pages are printed as immediately after the page from
        which they are displaced as possible.  If this element is not the first page float to be displaced from this page
        area to this page name, its contents should begin on the last page sheet of the floated page sequence previously
        established (unless precluded, for example by page-breaking properties).

... And add the example of float: 'top next page'...?

Floats are treated specially in many contexts (stacking leaps to mind), so there may be exceptions to general float behavior that need to be carved out for these somewhat different 'floats'.  That would apply to page floats in general, I think.

Best wishes,

Melinda
Received on Wednesday, 5 November 2008 21:04:35 GMT

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