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

[svgwg] Add getScreenBBox() method to SVGGraphicsElement interface

[svgwg] getPathSegAtLength had consistent implementation behavior for invalid paths

[svgwg] inline-base direction

[svgwg] Issue: getPathSegAtLength had consistent implementation behavior for invalid paths marked as SVG Paths

[svgwg] Issue: SVGAElement implements two conflicting interfaces marked as Linking chapter

[svgwg] Possible to use `<use xlink:href="#id">` in the presence of an HTML `<base>` element?

[svgwg] Remove SVGGeometryElement interface from <mesh>?

[svgwg] Rotating text

[svgwg] Scientific notation has been removed from the path EBNF

[svgwg] Since vector-effect options other than non-scaling-stroke already have multiple implementations, is the "at risk" flag valid?

[svgwg] SVG and CSS display:contents

[svgwg] SVG MIME Type (image/svg+xml) is misleading to developers

[svgwg] SVGAElement implements two conflicting interfaces

Closed: [svgwg] Remove SVGGeometryElement interface from <mesh>?

Last message date: Saturday, 29 April 2017 19:18:07 UTC