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

Thursday, 29 June 2017

• Re: [svgwg] SVG should specify what CSS attribute selectors and class selectors match on Tab Atkins Jr. via GitHub
• Re: [svgwg] overflow="auto" should be treated as hidden rather than visible David Bruchmann via GitHub
• Re: [svgwg] overflow="auto" should be treated as hidden rather than visible Amelia Bellamy-Royds via GitHub
• Re: [svgwg] overflow="auto" should be treated as hidden rather than visible David Bruchmann via GitHub
• Re: [svgwg] overflow="auto" should be treated as hidden rather than visible Amelia Bellamy-Royds via GitHub
• Re: [svgwg] overflow="auto" should be treated as hidden rather than visible Tom Shinnick via GitHub
• Re: [svgwg] overflow="auto" should be treated as hidden rather than visible Amelia Bellamy-Royds via GitHub
• Re: [svgwg] overflow="auto" should be treated as hidden rather than visible Tom Shinnick via GitHub

Wednesday, 28 June 2017

• [svgwg] Issue: overflow="auto" should be treated as hidden rather than visible marked as Rendering Model chapter Amelia Bellamy-Royds via GitHub
• Re: [svgwg] overflow="auto" should be treated as hidden rather than visible Amelia Bellamy-Royds via GitHub
• [svgwg] overflow="auto" should be treated as hidden rather than visible Robert Longson via GitHub

Tuesday, 27 June 2017

• Re: [svgwg] SVG should specify what CSS attribute selectors and class selectors match on Boris Zbarsky via GitHub
• Re: [svgwg] SVG should specify what CSS attribute selectors and class selectors match on Tab Atkins Jr. via GitHub
• Re: [svgwg] SVG should specify what CSS attribute selectors and class selectors match on Amelia Bellamy-Royds via GitHub
• Re: [svgwg] SVG should specify what CSS attribute selectors and class selectors match on Tab Atkins Jr. via GitHub
• [svgwg] Issue: SVG should specify what CSS attribute selectors and class selectors match on marked as SVG Core Brian Birtles via GitHub
• [svgwg] SVG should specify what CSS attribute selectors and class selectors match on Brian Birtles via GitHub

Friday, 23 June 2017

• Re: [svgwg] SVG MIME Type (image/svg+xml) is misleading to developers David Bruchmann via GitHub
• Re: [svgwg] SVG MIME Type (image/svg+xml) is misleading to developers David Bruchmann via GitHub
• Re: [svgwg] SVG MIME Type (image/svg+xml) is misleading to developers Jan Schwarzrock via GitHub
• Re: [svgwg] SVG MIME Type (image/svg+xml) is misleading to developers David Bruchmann via GitHub
• Re: [svgwg] SVG MIME Type (image/svg+xml) is misleading to developers David Bruchmann via GitHub
• [svgwg] Pull Request: Use stretchy parentheses for the arctan argument. Frédéric Wang via GitHub
• Re: [svgwg] SVG MIME Type (image/svg+xml) is misleading to developers David Bruchmann via GitHub
• Re: [svgwg] SVG MIME Type (image/svg+xml) is misleading to developers David Bruchmann via GitHub

Thursday, 15 June 2017

• Re: [svgwg] SVGTransform's setMatrix method should take a DOMMatrixInit Simon Pieters via GitHub
• [svgwg] SVGTransform's setMatrix method should take a DOMMatrixInit Simon Pieters via GitHub

Wednesday, 14 June 2017

• Re: [svgwg] grammar for "closepath can substitute for final coordinate" is broken Nikos Andronikos via GitHub
• Re: [svgwg] grammar for "closepath can substitute for final coordinate" is broken Nikos Andronikos via GitHub

Saturday, 10 June 2017

• Re: [svgwg] grammar for "closepath can substitute for final coordinate" is broken Amelia Bellamy-Royds via GitHub
• Re: [svgwg] grammar for "closepath can substitute for final coordinate" is broken Tom Shinnick via GitHub

Friday, 9 June 2017

• Re: [svgwg] Include SVGGraphicsElement#farthestViewportElement and nearestViewportElement in the spec Luna Lu via GitHub
• Re: [svgwg] grammar for "closepath can substitute for final coordinate" is broken Amelia Bellamy-Royds via GitHub
• [svgwg] grammar for "closepath can substitute for final coordinate" is broken Tom Shinnick via GitHub

Thursday, 8 June 2017

• [svgwg] C.4.2 out-of-range flag values note is invalid/unsupported, should be dropped Tom Shinnick via GitHub
• [svgwg] Issue: How does vector-effect=non-scaling-stroke interact with the stroke-dash* properties marked as SVG Core Amelia Bellamy-Royds via GitHub
• Re: [svgwg] How does vector-effect=non-scaling-stroke interact with the stroke-dash* properties Amelia Bellamy-Royds via GitHub

Wednesday, 7 June 2017

• [svgwg] How does vector-effect=non-scaling-stroke interact with the stroke-dash* properties Fredrik Söderqvist via GitHub

Monday, 5 June 2017

• [svgwg] Remove un-implemented `pointer-events` "painted" rules for images Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Remove un-implemented `pointer-events` "painted" rules for images marked as Scripting chapter Amelia Bellamy-Royds via GitHub

Last message date: Thursday, 29 June 2017 22:23:06 UTC