RE: [gcpm] border-parts

James said:
> > Håkon said:
> >
> > We're getting closer. I suggest:
> >
> >   The element is floated to one or more named pages of the type
> >   specified. These named pages are created for the purpose
> of showing
> >   the element, and they are presented as early as possible after the
> >   page from which they are displaced. If the element is not
> the first
> >   page float to be displaced from the current page
>
> Oops -- you might want to add "or from earlier pages" --
> Otherwise, the spec. does not consider the possibility of
> multiple earlier pages 'floating' to a later named page.
> Without this phrase, it seems to me that the sentence says
> that each new page with 'float(name)' would start a new page,
> not continue after all other floats which might have been
> sent to that named page, whether they came from the current
> page or from earlier pages.

The intent was to specify *where* in the output stream the pages should be printed.  If you add 'or from earlier pages, it's left unspecified.  How long does the UA buffer up page floats before printing them?  Do we want them at the end of the document?  I think not in the usual case.  It makes more sense to put them as near (after) their neighboring content as possible.  The 'after' is driven by the assumption that the neighboring content will often provide some reference to the information being displaced.

But I thought we had a 'last' page float keyword, which I was thinking would be the mechanism to push them to the end of the doc, and a quick check of gcpm indicates not.  Had you considered that, Håkon?

> I would also prefer (but not require) that the first sentence
> be clarified as to the reason the element might be floated to
> more than one page -- I guess because the element would not
> fit and could be split, but this is not very clear.

Maybe an example like a table that would spill onto a second page would make that clearer.

Best wishes,

Melinda

Received on Thursday, 6 November 2008 18:13:04 UTC