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

Hi all,

These are the changes I intend to commit to complete ACTION-3599 [1].
Looking for any feedback before I push.

----------------------------------------------------------------------
RESOLUTION: path/polygon/polyline with no data set (empty or zero valid
commands) should not render

Added to 8.2 The 'path' element:
"The lacuna value, (none) indicates that the path element is valid but
does not render."

Added to 9.6. The ‘polyline’ element:
The lacuna value, (none), indicates that the polyline element is valid
but does not render.

Added to 9.7. The ‘polygon’ element:
The lacuna value, (none), indicates that the polygon element is valid,
but does not render.

----------------------------------------------------------------------
RESOLUTION: getBBox for path/polygon/polyline with no data set (empty or
zero valid commands) should return [0,0,0,0]

Added to 7.11 Bounding boxes:
An element with no position specified (such as a 'path' element with a
value of (none) for the 'd' attribute) is positioned at the
point (0,0) for the purposes of calculating a bounding box.

Note there is already text defining that an element with no width or
height information is treated as having a width/height of zero.

----------------------------------------------------------------------
RESOLUTION: Bounding box for path/polygon/polyline with no data set
(empty or zero valid commands) should not contribute to ancestor
bounding box

Because these cases are now specified to not render, this requirement is met

----------------------------------------------------------------------
RESOLUTION: bounding box for path with some invalid data following some
valid data will include the data which is rendered

This is mostly already specified in C.2. Error processing [2].
The document should be rendered up to the point of the error. For
path,polyline and polygon elements this includes the valid path data or
valid points.

Added to 8.3.10 The grammar for path data:
"If path data not matching the grammar is encountered, then the path
data is in error (see Error Processing). "

Added to 9.7.1. The grammar for points specifications in ‘polyline’ and
‘polygon’ elements:
"If data not matching the grammar is encountered, then the points
specification is in error (see Error Processing). "

1. https://www.w3.org/Graphics/SVG/WG/track/actions/3599
2. http://www.w3.org/TR/SVG2/implnote.html#ErrorProcessing
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 Thursday, 24 April 2014 01:54:08 UTC