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

Tuesday, 28 February 2017

• Re: [svgwg] Include SVGGraphicsElement#farthestViewportElement and nearestViewportElement in the spec Nikos Andronikos via GitHub
• [svgwg] Issue: Include SVGGraphicsElement#farthestViewportElement and nearestViewportElement in the spec marked as SVG Core Nikos Andronikos via GitHub
• Closed: [svgwg] Standardize SVGTests#requiredFeatures Nikos Andronikos via GitHub
• Re: [svgwg] Standardize SVGTests#requiredFeatures Nikos Andronikos via GitHub

Friday, 24 February 2017

• [svgwg] Include SVGGraphicsElement#farthestViewportElement and nearestViewportElement in the spec Luna Lu via GitHub
• [svgwg] Standardize SVGTests#requiredFeatures Luna Lu via GitHub

Thursday, 23 February 2017

• [svgwg] Issue: getScreenCTM (and friends?) results for elements that are not in the rendering tree? marked as SVG Core Nikos Andronikos via GitHub

Wednesday, 22 February 2017

• [svgwg] getScreenCTM (and friends?) results for elements that are not in the rendering tree? Fredrik Söderqvist via GitHub

Friday, 17 February 2017

• [svgwg] Issue: Since vector - effect options other than non - scaling - stroke already have multiple implementations, is the "at risk" flag valid? marked as Entire spec Satoru Takagi via GitHub
• [svgwg] Since vector - effect options other than non - scaling - stroke already have multiple implementations, is the "at risk" flag valid? Satoru Takagi via GitHub

Monday, 13 February 2017

• Re: [svgwg] SVG and CSS display:contents Tab Atkins Jr. via GitHub
• Re: [svgwg] SVG and CSS display:contents Amelia Bellamy-Royds via GitHub
• [svgwg] SVG and CSS display:contents Rune Lillesveen via GitHub

Friday, 10 February 2017

• [svgwg] Pull Request: Remove explicit currentColor from <paint> Manish Goregaokar via GitHub

Last message date: Tuesday, 28 February 2017 22:41:29 UTC