public-svg-issues@w3.org from July 2017 by subject

[svgwg] Add `contenteditable` attribute for SVG text elements

[svgwg] Add a method to return the path direction (tangent) angle at a given distance

[svgwg] Compatibility mid-line rendering attribute to textPath

[svgwg] Contradiction in spec in regards to SVGUseElement.instanceRoot etc

[svgwg] Floating point number format discordance (SVG vs CSS vs browsers)

[svgwg] Issue: Add `contenteditable` attribute for SVG text elements marked as Interactivity chapter

[svgwg] Issue: Add a method to return the path direction (tangent) angle at a given distance marked as Basic Data Types and Interfaces chapter

[svgwg] Issue: Shorthand properties should be promoted to presentation attributes. marked as SVG Core

[svgwg] Issue: SVG marker orientation at a 180° U-turn not well defined marked as SVG Core

[svgwg] Issue: SVG2 path data coordinates are currently spec'd as integers. marked as SVG Core

[svgwg] Shorthand properties should be promoted to presentation attributes.

[svgwg] Show need for "segment-completing closepath" with curves/arcs

[svgwg] SVG marker orientation at a 180° U-turn not well defined

[svgwg] SVG2 path data coordinates are currently spec'd as integers.

[svgwg] Two questions about the `<a>` element

Closed: [svgwg] Contradiction in spec in regards to SVGUseElement.instanceRoot etc

Last message date: Monday, 31 July 2017 20:24:17 UTC