Re: What should the bbox of a path without a d attribute be?

My full reply is yet to come, just want to clarify one point

On 20/02/2014 4:29 AM, Erik Dahlström wrote:
>
>
<snip>
> For the sake of the discussion, here's an alternative model B:
>
> * elements that don't render must return bbox=[0,0,0,0]
> * elements that don't render don't contribute to any (conceptual)
> ancestor's bbox (thinking of container elements, but also of <use>)
>
> Model C:
>
> * elements that don't render must return bbox=[0,0,0,0]
> * elements that don't render do contribute to any (conceptual)
> ancestor's bbox
>
> Model D:
>
> * elements that don't render must return bbox=[x,y,w,h] with the
> values for x,y,w,h taken from the lacuna values as defined for each
> relevant attribute on the given element, and if there's nothing to
> fall back on use zero for the missing value(s) instead
> * elements that don't render don't contribute to any (conceptual)
> ancestor's bbox
>
> Model E:
>
> * elements that don't render must always return bbox=[x,y,w,h] with
> the values for x,y,w,h taken from the lacuna values as defined for
> each relevant attribute on the given element, and if there's nothing
> to fall back on use zeros instead
> * elements that don't render do contribute to any (conceptual)
> ancestor's bbox
<snip>

In all these cases, when you say "elements that don't render must return
bbox=[0,0,0,0]", do you mean just in the case where no positional or
dimensional attributes are given by the author?
Or, do you mean for models B and C that getBBox() will always return
[0,0,0,0] when rendering is disabled for an element and models D and E
refer to the currently specified behaviour (the spec currently says that
getBBox() always returns the bounding box as if rendering the shape).

Cheers,
Nikos
The information contained in this email message and any attachments may be confidential and may also be the subject to legal professional privilege. If you are not the intended recipient, any use, interference with, disclosure or copying of this material is unauthorised and prohibited. If you have received this email in error, please immediately advise the sender by return email and delete the information from your system.

Received on Friday, 21 February 2014 05:13:19 UTC