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

Amelia Bellamy-Royds via GitHub

• Re: [svgwg] Should we move more HTMLElement members to HTMLorSVGElement mixin? (Monday, 26 March)
• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 (Friday, 23 March)
• Re: [svgwg] Move dataset & other shared IDL attributes from SVGElement to HTMLOrSVGElement (Friday, 23 March)
• Re: [svgwg] Move dataset IDL attribute from SVGElement to Element (Friday, 23 March)
• [svgwg] Issue: Move dataset IDL attribute from SVGElement to Element marked as Needs editing (Friday, 23 March)
• Re: [svgwg] Should we move more HTMLElement members to HTMLorSVGElement mixin? (Friday, 23 March)
• Re: [svgwg] Implicit and allowed roles for SVG element in a HTML document (Friday, 23 March)
• Re: [svgwg] Implicit and allowed roles for SVG element in a HTML document (Friday, 23 March)
• Re: [svgwg] Does the entire path need to be valid in order to use a path attribute on a textPath (Tuesday, 20 March)
• [svgwg] Issue: Does the entire path need to be valid in order to use a path attribute on a textPath marked as Text chapter (Tuesday, 20 March)
• Re: [svgwg] dur attribute should permit leading . (Tuesday, 20 March)
• [svgwg] Issue: dur attribute should permit leading . marked as SVG Animations (Tuesday, 20 March)
• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 (Monday, 19 March)
• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 (Friday, 16 March)
• Re: [svgwg] SVGTextPathElement interface seems to be missing properties (Wednesday, 14 March)
• [svgwg] Issue: SVGTextPathElement interface seems to be missing properties marked as SVG Core (Wednesday, 14 March)
• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 (Sunday, 11 March)
• [svgwg] Issue: SVG 1.1 Errata: How to Proceed? marked as Tools (Monday, 5 March)
• [svgwg] SVG 1.1 Errata: How to Proceed? (Monday, 5 March)
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint (Saturday, 3 March)
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint (Saturday, 3 March)
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint (Saturday, 3 March)
• [svgwg] Issue: Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint marked as Document structure chapter (Saturday, 3 March)

Anne van Kesteren via GitHub

• Re: [svgwg] Move dataset IDL attribute from SVGElement to Element (Friday, 23 March)

Bogdan Brinza via GitHub

• [svgwg] Merged Pull Request: Fixes #345 Add [Exposed] to SVG interfaces (Thursday, 22 March)
• Closed: [svgwg] Add [Exposed] to all interfaces (Thursday, 22 March)
• [svgwg] new commits pushed by boggydigital (Thursday, 22 March)

CSS Meeting Bot via GitHub

• Re: [svgwg] Move dataset & other shared IDL attributes from SVGElement to HTMLOrSVGElement (Monday, 26 March)
• Re: [svgwg] Should we move more HTMLElement members to HTMLorSVGElement mixin? (Monday, 26 March)
• Re: [svgwg] SVGAElement all attributes except href should be as HTML i.e. not SVGAnimatedString (Monday, 26 March)
• Re: [svgwg] SVGAElement all attributes except href should be as HTML i.e. not SVGAnimatedString (Monday, 19 March)
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint (Monday, 5 March)

David Storey via GitHub

• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 (Thursday, 29 March)
• Re: [svgwg] Should we move more HTMLElement members to HTMLorSVGElement mixin? (Saturday, 24 March)
• Re: [svgwg] Should we move more HTMLElement members to HTMLorSVGElement mixin? (Saturday, 24 March)
• Re: [svgwg] Should we move more HTMLElement members to HTMLorSVGElement mixin? (Friday, 23 March)
• [svgwg] Should we move more HTMLElement members to HTMLorSVGElement mixin? (Friday, 23 March)
• [svgwg] Issue: Should we move more HTMLElement members to HTMLorSVGElement mixin? marked as Agenda+ (Friday, 23 March)
• Re: [svgwg] Implicit and allowed roles for SVG element in a HTML document (Friday, 23 March)
• Re: [svgwg] Move dataset IDL attribute from SVGElement to Element (Friday, 23 March)
• Re: [svgwg] SVGAElement all attributes except href should be as HTML i.e. not SVGAnimatedString (Tuesday, 20 March)
• Re: [svgwg] SVGAElement all attributes except href should be as HTML i.e. not SVGAnimatedString (Tuesday, 20 March)
• Re: [svgwg] SVGAElement all attributes except href should be as HTML i.e. not SVGAnimatedString (Tuesday, 20 March)
• Re: [svgwg] SVGAElement all attributes except href should be as HTML i.e. not SVGAnimatedString (Monday, 19 March)
• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 (Monday, 19 March)
• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 (Thursday, 15 March)
• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 (Thursday, 15 March)
• Re: [svgwg] SVGAElement all attributes except href should be as HTML i.e. not SVGAnimatedString (Monday, 12 March)
• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 (Monday, 12 March)
• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 (Monday, 12 March)
• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 (Friday, 9 March)
• Re: [svgwg] Fixes #345 Add [Exposed] to SVG interfaces (Friday, 9 March)
• Re: [svgwg] Move dataset IDL attribute from SVGElement to Element (Wednesday, 7 March)

Domenic Denicola via GitHub

• Re: [svgwg] Move dataset & other shared IDL attributes from SVGElement to HTMLOrSVGElement (Saturday, 24 March)
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint (Wednesday, 7 March)

Eric Willigers via GitHub

• [svgwg] Pull Request: Remove support for segment-completing close path (Friday, 30 March)
• [svgwg] Merged Pull Request: Remove path rotation requirement (Friday, 30 March)
• [svgwg] new commits pushed by ewilligers (Friday, 30 March)
• [svgwg] Pull Request: Remove path rotation requirement (Friday, 30 March)

Fredrik Söderqvist via GitHub

• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint (Saturday, 3 March)
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint (Saturday, 3 March)

Hayato Ito via GitHub

• Re: [svgwg] "mode" of a shadow root which <use> element uses is unclear (Wednesday, 28 March)
• [svgwg] "mode" of a shadow root which <use> element uses is unclear (Wednesday, 28 March)

Jarek Foksa via GitHub

• [svgwg] Add <a> to "text content element" category (Saturday, 31 March)
• [svgwg] Remove "text content child element" category and add <a> to "text content element" category (Saturday, 31 March)

Liam Quin via GitHub

• Re: [svgwg] SVGAElement all attributes except href should be as HTML i.e. not SVGAnimatedString (Tuesday, 20 March)
• [svgwg] Issue: SVGAElement all attributes except href should be as HTML i.e. not SVGAnimatedString marked as agenda+ (Tuesday, 20 March)
• Re: [svgwg] SVGAElement all attributes except href should be as HTML i.e. not SVGAnimatedString (Monday, 19 March)
• Re: [svgwg] SVGAElement all attributes except href should be as HTML i.e. not SVGAnimatedString (Monday, 19 March)
• [svgwg] Review of L.2.1 changes across the whole document - status (Thursday, 15 March)
• [svgwg] Issue: Review of L.2.1 changes across the whole document - status marked as Entire spec (Thursday, 15 March)

Philip Rogers via GitHub

• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint (Saturday, 3 March)

Robert Longson via GitHub

• Re: [svgwg] dur attribute should permit leading . (Tuesday, 20 March)
• [svgwg] dur attribute should permit leading . (Tuesday, 20 March)
• [svgwg] Does the entire path need to be valid in order to use a path attribute on a textPath (Tuesday, 20 March)
• Re: [svgwg] Review implementation support - Paths chapter (Sunday, 18 March)
• [svgwg] SVGTextPathElement interface seems to be missing properties (Wednesday, 14 March)
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint (Saturday, 3 March)
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint (Saturday, 3 March)
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint (Saturday, 3 March)

Sangwhan

• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 (Tuesday, 20 March)
• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 (Monday, 19 March)

Tab Atkins Jr. via GitHub

• Re: [svgwg] Should we move more HTMLElement members to HTMLorSVGElement mixin? (Monday, 26 March)
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint (Saturday, 3 March)
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint (Saturday, 3 March)

Tobie Langel via GitHub

• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 (Monday, 19 March)
• Re: [svgwg] Fixes #345 Add [Exposed] to SVG interfaces (Friday, 9 March)

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