issues in DFXP draft

A few minor issues:

{any attribute in ...}

I've had a couple of questions internally whether this means one or many. Could we clarify the language to
{any set of attributes in ...}

-----

Typo in 7.1.4 (addition in [[]]) :
When rendered on a continuous (non-paged) visual presentation medium, a div element is expected to generate a one or more block areas that contains zero or more child block areas generated by the div element's descendant p [[or div]] elements.

------

tts:backgroundColor

CSS (referenced through XSL) defines: "The background of the root element becomes the background of the canvas and covers the entire canvas, anchored (for 'background-position') at the same point as it would be if it was painted only for the root element itself. The root element does not paint this background again."

My interpretation of the canvas background is that is the plane on which the blocks are laid out, and then this is seen through the viewport-area of the region (which is equal to the content area). Can we clarify if this is correct, and which element (if any) controls the background colour of the canvas (and thus the content area), or whether it is always transparent. (My working assumption has been that it is the <body> element which controls it).

------
tts:extent
"The tts:extent attribute is used to specify the width and height of a region area (which may be the root container region)."

The semantics of this seem to imply that the root container is a region, which calls into question whether it is styled, has padding etc. Perhaps:

The tts:extent attribute is used on regions to specify the width and height of that region area, or on the tt element to specify the width and height of the root container.

Also - what would it mean to specify tts:extent="auto" on the tt element? Should we ban this usage.

-------

tts:overflow
"region composition and layout must be performed as if the region's width and height were infinite"

This seems to imply that the region background should have infinite extent too? I thought rather it implied that the initial containing block has infinite extent and that no clipping was performed by the region (as the example rendering shows).
Could we clarify this sentence.


tts:padding
The example rendering here obscures what the bottom edge padding would look like if the <p> region were not conveniently the right height. It may not be possible, but could we change this example to contain a slightly taller region.


Sean

Received on Friday, 24 April 2009 14:00:08 UTC