public-svg-issues@w3.org from March 2018 by date

Saturday, 31 March 2018

• [svgwg] Add <a> to "text content element" category Jarek Foksa via GitHub
• [svgwg] Remove "text content child element" category and add <a> to "text content element" category Jarek Foksa via GitHub

Friday, 30 March 2018

• [svgwg] Pull Request: Remove support for segment-completing close path Eric Willigers via GitHub
• [svgwg] Merged Pull Request: Remove path rotation requirement Eric Willigers via GitHub
• [svgwg] new commits pushed by ewilligers Eric Willigers via GitHub
• [svgwg] Pull Request: Remove path rotation requirement Eric Willigers via GitHub

Thursday, 29 March 2018

• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 David Storey via GitHub

Wednesday, 28 March 2018

• Re: [svgwg] "mode" of a shadow root which <use> element uses is unclear Hayato Ito via GitHub
• [svgwg] "mode" of a shadow root which <use> element uses is unclear Hayato Ito via GitHub

Monday, 26 March 2018

• Re: [svgwg] Should we move more HTMLElement members to HTMLorSVGElement mixin? Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Should we move more HTMLElement members to HTMLorSVGElement mixin? Tab Atkins Jr. via GitHub
• Re: [svgwg] Move dataset & other shared IDL attributes from SVGElement to HTMLOrSVGElement CSS Meeting Bot via GitHub
• Re: [svgwg] Should we move more HTMLElement members to HTMLorSVGElement mixin? CSS Meeting Bot via GitHub
• Re: [svgwg] SVGAElement all attributes except href should be as HTML i.e. not SVGAnimatedString CSS Meeting Bot via GitHub

Saturday, 24 March 2018

• Re: [svgwg] Move dataset & other shared IDL attributes from SVGElement to HTMLOrSVGElement Domenic Denicola via GitHub
• Re: [svgwg] Should we move more HTMLElement members to HTMLorSVGElement mixin? David Storey via GitHub
• Re: [svgwg] Should we move more HTMLElement members to HTMLorSVGElement mixin? David Storey via GitHub

Friday, 23 March 2018

• Re: [svgwg] Should we move more HTMLElement members to HTMLorSVGElement mixin? David Storey via GitHub
• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Move dataset & other shared IDL attributes from SVGElement to HTMLOrSVGElement Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Move dataset IDL attribute from SVGElement to Element Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Move dataset IDL attribute from SVGElement to Element marked as Needs editing Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Should we move more HTMLElement members to HTMLorSVGElement mixin? Amelia Bellamy-Royds via GitHub
• [svgwg] Should we move more HTMLElement members to HTMLorSVGElement mixin? David Storey via GitHub
• [svgwg] Issue: Should we move more HTMLElement members to HTMLorSVGElement mixin? marked as Agenda+ David Storey via GitHub
• Re: [svgwg] Implicit and allowed roles for SVG element in a HTML document Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Implicit and allowed roles for SVG element in a HTML document Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Move dataset IDL attribute from SVGElement to Element Anne van Kesteren via GitHub
• Re: [svgwg] Implicit and allowed roles for SVG element in a HTML document David Storey via GitHub
• Re: [svgwg] Move dataset IDL attribute from SVGElement to Element David Storey via GitHub

Thursday, 22 March 2018

• Closed: [svgwg] Add [Exposed] to all interfaces Bogdan Brinza via GitHub
• [svgwg] Merged Pull Request: Fixes #345 Add [Exposed] to SVG interfaces Bogdan Brinza via GitHub
• [svgwg] new commits pushed by boggydigital Bogdan Brinza via GitHub

Tuesday, 20 March 2018

• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 Sangwhan
• Re: [svgwg] dur attribute should permit leading . Robert Longson via GitHub
• Re: [svgwg] SVGAElement all attributes except href should be as HTML i.e. not SVGAnimatedString David Storey via GitHub
• Re: [svgwg] SVGAElement all attributes except href should be as HTML i.e. not SVGAnimatedString David Storey via GitHub
• Re: [svgwg] SVGAElement all attributes except href should be as HTML i.e. not SVGAnimatedString Liam Quin via GitHub
• [svgwg] Issue: SVGAElement all attributes except href should be as HTML i.e. not SVGAnimatedString marked as agenda+ Liam Quin via GitHub
• Re: [svgwg] SVGAElement all attributes except href should be as HTML i.e. not SVGAnimatedString David Storey via GitHub
• Re: [svgwg] Does the entire path need to be valid in order to use a path attribute on a textPath Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Does the entire path need to be valid in order to use a path attribute on a textPath marked as Text chapter Amelia Bellamy-Royds via GitHub
• Re: [svgwg] dur attribute should permit leading . Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: dur attribute should permit leading . marked as SVG Animations Amelia Bellamy-Royds via GitHub
• [svgwg] dur attribute should permit leading . Robert Longson via GitHub
• [svgwg] Does the entire path need to be valid in order to use a path attribute on a textPath Robert Longson via GitHub

Monday, 19 March 2018

• Re: [svgwg] SVGAElement all attributes except href should be as HTML i.e. not SVGAnimatedString David Storey via GitHub
• Re: [svgwg] SVGAElement all attributes except href should be as HTML i.e. not SVGAnimatedString CSS Meeting Bot via GitHub
• Re: [svgwg] SVGAElement all attributes except href should be as HTML i.e. not SVGAnimatedString Liam Quin via GitHub
• Re: [svgwg] SVGAElement all attributes except href should be as HTML i.e. not SVGAnimatedString Liam Quin via GitHub
• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 Tobie Langel via GitHub
• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 Sangwhan
• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 David Storey via GitHub

Sunday, 18 March 2018

• Re: [svgwg] Review implementation support - Paths chapter Robert Longson via GitHub

Friday, 16 March 2018

• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 Amelia Bellamy-Royds via GitHub

Thursday, 15 March 2018

• [svgwg] Review of L.2.1 changes across the whole document - status Liam Quin via GitHub
• [svgwg] Issue: Review of L.2.1 changes across the whole document - status marked as Entire spec Liam Quin via GitHub
• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 David Storey via GitHub
• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 David Storey via GitHub

Wednesday, 14 March 2018

• Re: [svgwg] SVGTextPathElement interface seems to be missing properties Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: SVGTextPathElement interface seems to be missing properties marked as SVG Core Amelia Bellamy-Royds via GitHub
• [svgwg] SVGTextPathElement interface seems to be missing properties Robert Longson via GitHub

Monday, 12 March 2018

• Re: [svgwg] SVGAElement all attributes except href should be as HTML i.e. not SVGAnimatedString David Storey via GitHub
• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 David Storey via GitHub
• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 David Storey via GitHub

Sunday, 11 March 2018

• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 Amelia Bellamy-Royds via GitHub

Friday, 9 March 2018

• Re: [svgwg] Fixes #345 Add [Exposed] to SVG interfaces Tobie Langel via GitHub
• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 David Storey via GitHub
• Re: [svgwg] Fixes #345 Add [Exposed] to SVG interfaces David Storey via GitHub

Wednesday, 7 March 2018

• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint Domenic Denicola via GitHub
• Re: [svgwg] Move dataset IDL attribute from SVGElement to Element David Storey via GitHub

Monday, 5 March 2018

• [svgwg] Issue: SVG 1.1 Errata: How to Proceed? marked as Tools Amelia Bellamy-Royds via GitHub
• [svgwg] SVG 1.1 Errata: How to Proceed? Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint CSS Meeting Bot via GitHub

Saturday, 3 March 2018

• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint Fredrik Söderqvist via GitHub
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint Fredrik Söderqvist via GitHub
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint Robert Longson via GitHub
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint Robert Longson via GitHub
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint Tab Atkins Jr. via GitHub
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint Philip Rogers via GitHub
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint Robert Longson via GitHub
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint marked as Document structure chapter Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint Tab Atkins Jr. via GitHub

Last message date: Saturday, 31 March 2018 20:12:38 UTC