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

RE: [gcpm] border-parts

From: Håkon Wium Lie <howcome@opera.com>
Date: Wed, 5 Nov 2008 11:21:36 +0100
Message-ID: <18705.29616.237674.232907@opera.com>
To: "Grant, Melinda" <melinda.grant@hp.com>
Cc: "www-style@w3.org" <www-style@w3.org>

Also sprach Grant, Melinda:

 > >   In this example, wide tables are floated to landscape pages:
 > >
 > >     table.wide {
 > >       float: page(landscape);
 > >     }
 > 
 > Seems good added flexibility. Where in the printed output should
 > the table appear? Immediately after the page from which it was
 > displaced? At the end of the document? Up to the UA? Do we want to
 > provide a control knob?

All these are options. Personally, I'd opt for a simple knob-less
solution were the page appears as early as possible. It may not be
possible to always use the next page. For example, it could come into
conflict with this:

  .figure { 
    float: top next page;
  }

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.

 > If two or more tables with class 'wide' are encountered within a
 > document, do they get printed on separate media sheets, or are the
 > tables both printed on the same sheet if they fit? (Probably some
 > dependency on the previous answer...)

I think same-sheet should be allowed (it's easy enough to set page
breaks if necessary) if a named page is in place and has room. No?

-h&kon

              Håkon Wium Lie                          CTO °þe®ª
howcome@opera.com                  http://people.opera.com/howcome
Received on Wednesday, 5 November 2008 10:23:01 GMT

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