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

[svgwg] Issue: Include SVGGraphicsElement#farthestViewportElement and nearestViewportElement in the spec marked as SVG Core Nikos Andronikos via GitHub (Tuesday, 28 February)

[svgwg] Include SVGGraphicsElement#farthestViewportElement and nearestViewportElement in the spec Luna Lu via GitHub (Friday, 24 February)

[svgwg] Standardize SVGTests#requiredFeatures Luna Lu via GitHub (Friday, 24 February)

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

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

[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 (Friday, 17 February)

[svgwg] Since vector - effect options other than non - scaling - stroke already have multiple implementations, is the "at risk" flag valid? Satoru Takagi via GitHub (Friday, 17 February)

[svgwg] SVG and CSS display:contents Rune Lillesveen via GitHub (Monday, 13 February)

[svgwg] Pull Request: Remove explicit currentColor from <paint> Manish Goregaokar via GitHub (Friday, 10 February)

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