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

Saturday, 29 April 2017

• Re: [svgwg] Scientific notation has been removed from the path EBNF Amelia Bellamy-Royds via GitHub

Monday, 24 April 2017

• Re: [svgwg] inline-base direction r12a via GitHub
• Re: [svgwg] Rotating text r12a via GitHub
• Re: [svgwg] getPathSegAtLength had consistent implementation behavior for invalid paths Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: getPathSegAtLength had consistent implementation behavior for invalid paths marked as SVG Paths Amelia Bellamy-Royds via GitHub
• [svgwg] getPathSegAtLength had consistent implementation behavior for invalid paths Philip Rogers via GitHub

Thursday, 20 April 2017

• Re: [svgwg] SVG and CSS display:contents Tab Atkins Jr. via GitHub

Wednesday, 19 April 2017

• Re: [svgwg] SVG and CSS display:contents Amelia Bellamy-Royds via GitHub
• Re: [svgwg] SVG and CSS display:contents L. David Baron via GitHub

Tuesday, 18 April 2017

• Re: [svgwg] SVG MIME Type (image/svg+xml) is misleading to developers Ty Whalin via GitHub

Saturday, 8 April 2017

• [svgwg] Issue: SVGAElement implements two conflicting interfaces marked as Linking chapter Amelia Bellamy-Royds via GitHub
• Re: [svgwg] SVGAElement implements two conflicting interfaces Amelia Bellamy-Royds via GitHub

Wednesday, 5 April 2017

• [svgwg] SVGAElement implements two conflicting interfaces Kagami Sascha Rosylight via GitHub

Tuesday, 4 April 2017

• Re: [svgwg] Since vector-effect options other than non-scaling-stroke already have multiple implementations, is the "at risk" flag valid? Tab Atkins Jr. via GitHub
• Re: [svgwg] Since vector-effect options other than non-scaling-stroke already have multiple implementations, is the "at risk" flag valid? 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? Nikos Andronikos via GitHub
• Re: [svgwg] Possible to use `<use xlink:href="#id">` in the presence of an HTML `<base>` element? Robert Longson via GitHub

Monday, 3 April 2017

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

Sunday, 2 April 2017

• Re: [svgwg] Add getScreenBBox() method to SVGGraphicsElement interface Fredrik Söderqvist via GitHub
• Re: [svgwg] Add getScreenBBox() method to SVGGraphicsElement interface Jarek Foksa via GitHub
• Re: [svgwg] Add getScreenBBox() method to SVGGraphicsElement interface Fredrik Söderqvist via GitHub

Saturday, 1 April 2017

• Re: [svgwg] Remove SVGGeometryElement interface from <mesh>? Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Remove SVGGeometryElement interface from <mesh>? Paul LeBeau via GitHub
• Closed: [svgwg] Remove SVGGeometryElement interface from <mesh>? Paul LeBeau via GitHub

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