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

Amelia Bellamy-Royds via GitHub

• Re: [svgwg] Scientific notation has been removed from the path EBNF (Saturday, 29 April)
• Re: [svgwg] getPathSegAtLength had consistent implementation behavior for invalid paths (Monday, 24 April)
• [svgwg] Issue: getPathSegAtLength had consistent implementation behavior for invalid paths marked as SVG Paths (Monday, 24 April)
• Re: [svgwg] SVG and CSS display:contents (Wednesday, 19 April)
• [svgwg] Issue: SVGAElement implements two conflicting interfaces marked as Linking chapter (Saturday, 8 April)
• Re: [svgwg] SVGAElement implements two conflicting interfaces (Saturday, 8 April)
• Re: [svgwg] Remove SVGGeometryElement interface from <mesh>? (Saturday, 1 April)

Chris Lilley via GitHub

• Re: [svgwg] Since vector-effect options other than non-scaling-stroke already have multiple implementations, is the "at risk" flag valid? (Tuesday, 4 April)

Fredrik Söderqvist via GitHub

• Re: [svgwg] Add getScreenBBox() method to SVGGraphicsElement interface (Sunday, 2 April)
• Re: [svgwg] Add getScreenBBox() method to SVGGraphicsElement interface (Sunday, 2 April)

Jarek Foksa via GitHub

• Re: [svgwg] Since vector-effect options other than non-scaling-stroke already have multiple implementations, is the "at risk" flag valid? (Monday, 3 April)
• Re: [svgwg] Add getScreenBBox() method to SVGGraphicsElement interface (Monday, 3 April)
• Re: [svgwg] Add getScreenBBox() method to SVGGraphicsElement interface (Sunday, 2 April)

Kagami Sascha Rosylight via GitHub

• [svgwg] SVGAElement implements two conflicting interfaces (Wednesday, 5 April)

L. David Baron via GitHub

• Re: [svgwg] SVG and CSS display:contents (Wednesday, 19 April)

Nikos Andronikos via GitHub

• Re: [svgwg] Since vector-effect options other than non-scaling-stroke already have multiple implementations, is the "at risk" flag valid? (Tuesday, 4 April)

Paul LeBeau via GitHub

• Re: [svgwg] Remove SVGGeometryElement interface from <mesh>? (Saturday, 1 April)
• Closed: [svgwg] Remove SVGGeometryElement interface from <mesh>? (Saturday, 1 April)

Philip Rogers via GitHub

• [svgwg] getPathSegAtLength had consistent implementation behavior for invalid paths (Monday, 24 April)

r12a via GitHub

• Re: [svgwg] inline-base direction (Monday, 24 April)
• Re: [svgwg] Rotating text (Monday, 24 April)

Robert Longson via GitHub

• Re: [svgwg] Possible to use `<use xlink:href="#id">` in the presence of an HTML `<base>` element? (Tuesday, 4 April)

Tab Atkins Jr. via GitHub

• Re: [svgwg] SVG and CSS display:contents (Thursday, 20 April)
• Re: [svgwg] Since vector-effect options other than non-scaling-stroke already have multiple implementations, is the "at risk" flag valid? (Tuesday, 4 April)

Ty Whalin via GitHub

• Re: [svgwg] SVG MIME Type (image/svg+xml) is misleading to developers (Tuesday, 18 April)

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