ISSUE-100: No fill unit for content area, and block and inline units not well specified
No fill unit for content area, and block and inline units not well specified
- Raised by:
- Sean Hayes
- Opened on:
- In Johns original requirements the concept of block seems to have been be a â€˜region-fullâ€™ at a time, rather than a timed text or an XSL:FO block. There is no current fill unit that corresponds to Johns idea of filling up the region (or clearing) as much as possible at each fill interval. I propose we remove the â€œblockâ€ fill unit, and replace it with something to indicate using as much as possible of the flow buffer to fill the content area of the region without overflow.
If not, we need to clarify what is actually meant by a block level fill unit (<p>, <div> <body>?), especially if the content can contain nested blocks, and what happens if the block is actually too big for the region.
Similarly â€œinlineâ€ (fragment in Johns terms) is not well defined now either, since we have adopted nested inlines.
- Related Actions Items:
- No related actions
- Related emails:
- Agenda for meeting 22-05-09 (from Sean.Hayes@microsoft.com on 2009-05-22)
- ISSUE-100 (Fill units): No fill unit for content area, and block and inline units not well specified (from firstname.lastname@example.org on 2009-05-15)
resolved in TTAF1-DFXP WD Editor's Copy Update - 20090529Glenn Adams, 29 May 2009, 04:33:42
Display change log