This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 28535 - Missing definition for 'shape-rendering' property, or bad example provided
Summary: Missing definition for 'shape-rendering' property, or bad example provided
Status: NEW
Alias: None
Product: SVG
Classification: Unclassified
Component: Styling (show other bugs)
Version: SVG 1.1 Full
Hardware: PC Windows NT
: P2 normal
Target Milestone: Test Suite
Assignee: Doug Schepers
QA Contact: SVG Public List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-22 14:32 UTC by Tristan Bailey
Modified: 2015-04-22 14:32 UTC (History)
0 users

See Also:


Attachments

Description Tristan Bailey 2015-04-22 14:32:19 UTC
Under '5 Document Structure' of the SVG 1.1 Second Edition specification, the example titled 'Example Use04' contains the following line:

/* rule 7 */ use > path { shape-rendering: optimizeQuality }

However, no definition exists for an 'optimizeQuality' value of the 'shape-rendering' property, as can be seen via the following link:

11.7.3 The ‘shape-rendering’ property
http://www.w3.org/TR/SVG/painting.html#ShapeRenderingProperty

It has been suggested on the Internet that the 'optimizeQuality' value implies that anti-aliasing is used.

Both the 'optimizeSpeed' and 'crispEdges' values discuss the turning off of such a feature. It is not made clear if either the 'auto' or 'geometricPrecision' values make use of anti-aliasing.

Suggestions:
- Look at the definitions for 'optimizeSpeed' and crispEdges', and determine if they should be made clearer as far as anti-aliasing is concerned.
- Determine whether or not the 'optimizeQuality' value is valid. If so, declare it. If not, remove it from the example.