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

Amelia Bellamy-Royds via GitHub

• Re: [svgwg] SVG and CSS display:contents (Monday, 13 February)

Fredrik Söderqvist via GitHub

• [svgwg] getScreenCTM (and friends?) results for elements that are not in the rendering tree? (Wednesday, 22 February)

Luna Lu via GitHub

• [svgwg] Include SVGGraphicsElement#farthestViewportElement and nearestViewportElement in the spec (Friday, 24 February)
• [svgwg] Standardize SVGTests#requiredFeatures (Friday, 24 February)

Manish Goregaokar via GitHub

• [svgwg] Pull Request: Remove explicit currentColor from <paint> (Friday, 10 February)

Nikos Andronikos via GitHub

• Re: [svgwg] Include SVGGraphicsElement#farthestViewportElement and nearestViewportElement in the spec (Tuesday, 28 February)
• [svgwg] Issue: Include SVGGraphicsElement#farthestViewportElement and nearestViewportElement in the spec marked as SVG Core (Tuesday, 28 February)
• Closed: [svgwg] Standardize SVGTests#requiredFeatures (Tuesday, 28 February)
• Re: [svgwg] Standardize SVGTests#requiredFeatures (Tuesday, 28 February)
• [svgwg] Issue: getScreenCTM (and friends?) results for elements that are not in the rendering tree? marked as SVG Core (Thursday, 23 February)

Rune Lillesveen via GitHub

• [svgwg] SVG and CSS display:contents (Monday, 13 February)

Satoru Takagi via GitHub

• [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 (Friday, 17 February)
• [svgwg] Since vector - effect options other than non - scaling - stroke already have multiple implementations, is the "at risk" flag valid? (Friday, 17 February)

Tab Atkins Jr. via GitHub

• Re: [svgwg] SVG and CSS display:contents (Monday, 13 February)

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