Re: spec question - extent

I don¹t see as unusual or illogical at all. If I want to design a particular
layout for regions, then I have to make certain assumptions about the
coordinate space in which those regions are placed, which is precisely the
intent of tts:extent on body. If you recall, we had earlier placed this
property on <tt:tt/> rather than <tt:body/>, but some commenters felt
strongly it should be on the latter, so we moved it. I was opposed to that
change, however, so I would not mind moving it back to the way we had it.
For me, tts:extent on body is similar to specifying width and height
properties on an <svg/> element in SVG. Similarly, it would be best to
express this on <tt/>.


On 12/10/08 7:24 AM, "Sean Hayes" <Sean.Hayes@microsoft.com> wrote:

> I¹m confused by the definition of the extent property:
>  
> ³The root container extent is determined either by a tts:extent specified on
> the body element, if present, or by the external authoring context, if not
> present. In the former case, if the width and height is expressed in terms of
> two <length> specifications, then these specifications must be expressed as
> non-percentage, definite lengths using pixel units.²
>  
> I¹m not sure we should even be considering shaping the external root
> container, but if we are, then since body elements are notionally re-parented
> inside regions, it seems illogical to me that the body would specify the
> extent of the root container in which regions are placed. It would make more
> sense to me in such a case if extent applied to apply to layout and region,
> the former setting the authoring context, and the latter setting the regions
> within that context.
>  
> Sean Hayes
> Media Accessibility Strategist
> Accessibility Business Unit
> Microsoft
>  
> Office:  +44 118 909 5867,
> Mobile: +44 7875 091385
>  
>