public-svg-issues@w3.org from November 2016 by date

Friday, 25 November 2016

• Re: [svgwg] The expressions and illustrations in the vector effects chapter of SVG 2 CR are broken. Nikos Andronikos via GitHub
• Re: [svgwg] The expressions and illustrations in the vector effects chapter of SVG 2 CR are broken. Nikos Andronikos via GitHub

Thursday, 24 November 2016

• Re: [svgwg] patternTransform browser implementations do not match spec Amelia Bellamy-Royds via GitHub
• Re: [svgwg] The expressions and illustrations in the vector effects chapter of SVG 2 CR are broken. Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: The expressions and illustrations in the vector effects chapter of SVG 2 CR are broken. marked as Needs editing Satoru Takagi via GitHub
• [svgwg] The expressions and illustrations in the vector effects chapter of SVG 2 CR are broken. Satoru Takagi via GitHub
• Closed: [svgwg] SVGUseElementShadowRoot section defines wrong IDL interface Amelia Bellamy-Royds via GitHub
• Re: [svgwg] patternTransform browser implementations do not match spec Nikos Andronikos via GitHub

Wednesday, 23 November 2016

• [svgwg] Pull Request: Correct SVGUseElementShadowRoot interface definition. Closes #290. Nikos Andronikos via GitHub

Tuesday, 22 November 2016

• Re: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript Nikos Andronikos via GitHub
• Closed: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript Nikos Andronikos via GitHub
• Re: [svgwg] Make SVGUnitTypes a regular interface with only constants Philippe Le Hegaret via GitHub
• Re: [svgwg] SVG MIME Type (image/svg+xml) is misleading to developers Nikos Andronikos via GitHub

Monday, 21 November 2016

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

Friday, 18 November 2016

• Re: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript Philip Jägenstedt via GitHub
• Re: [svgwg] Interaction of `x` attribute and `startOffset` in a textPath element. Nikos Andronikos via GitHub
• [svgwg] Issue: Interaction of `x` attribute and `startOffset` in a textPath element. marked as Needs editing Nikos Andronikos via GitHub

Thursday, 17 November 2016

• Re: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript Nikos Andronikos via GitHub
• Re: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript Philip Jägenstedt via GitHub
• Re: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript Robert Longson via GitHub
• Re: [svgwg] Make SVGUnitTypes a regular interface with only constants Philip Jägenstedt via GitHub
• Re: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript Philip Jägenstedt via GitHub
• Re: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript Nikos Andronikos via GitHub

Wednesday, 16 November 2016

• [svgwg] Pull Request: Make SVGUnitTypes a regular interface with only constants Nikos Andronikos via GitHub
• Re: [svgwg] Make SVGUnitTypes a regular interface with only constants Nikos Andronikos via GitHub
• Re: [svgwg] Make SVGUnitTypes a regular interface with only constants Philip Jägenstedt via GitHub
• Re: [svgwg] Make SVGUnitTypes a regular interface with only constants Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Make SVGUnitTypes a regular interface with only constants Philip Jägenstedt via GitHub
• Re: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript Philip Jägenstedt via GitHub
• [svgwg] Pull Request: Make SVGUnitTypes a regular interface with only constants Philip Jägenstedt via GitHub
• Re: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript Philip Jägenstedt via GitHub
• Re: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript Bogdan Brinza via GitHub
• Re: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript Philip Jägenstedt via GitHub
• Re: [svgwg] Copy Editing: Eradicate the usage of informal `you'; clean up surrounding text Nikos Andronikos via GitHub
• Re: [svgwg] Copy Editing: Eradicate the usage of informal `you'; clean up surrounding text Nikos Andronikos via GitHub

Tuesday, 15 November 2016

• [svgwg] Pull Request: Copy Editing: Eradicate the usage of informal `you'; clean up surrounding text Michael Witten via GitHub

Friday, 11 November 2016

• Re: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript Bogdan Brinza via GitHub

Thursday, 10 November 2016

• Re: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript Nikos Andronikos via GitHub

Wednesday, 9 November 2016

• Re: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript Philip Jägenstedt via GitHub
• Re: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript Robert Longson via GitHub
• Re: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript Boris Zbarsky via GitHub
• Re: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript Boris Zbarsky via GitHub
• Re: [svgwg] Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript Philip Jägenstedt via GitHub
• Re: [svgwg] patternTransform browser implementations do not match spec Tavmjong via GitHub
• Re: [svgwg] patternTransform browser implementations do not match spec Amelia Bellamy-Royds via GitHub
• [svgwg] patternTransform browser implementations do not match spec Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: patternTransform browser implementations do not match spec marked as Needs CSS WG Amelia Bellamy-Royds via GitHub

Wednesday, 2 November 2016

• Re: [svgwg] SVGPathElement and SVGGeometryElement in http://w3c-test.org/svg/interfaces.html do not match current specification Nikos Andronikos via GitHub
• Closed: [svgwg] SVGPathElement and SVGGeometryElement in http://w3c-test.org/svg/interfaces.html do not match current specification Nikos Andronikos via GitHub

Tuesday, 1 November 2016

• Re: [svgwg] Decide what to do with zoom and pan Robert Longson via GitHub
• [svgwg] Issue: SVGPathElement and SVGGeometryElement in http://w3c-test.org/svg/interfaces.html do not match current specification marked as Test suite Nikos Andronikos via GitHub

Last message date: Friday, 25 November 2016 00:54:56 UTC