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

Friday, 29 July 2016

• Closed: [svgwg] Update content models with <audio>, <video>, <canvas> and <iframe> Nikos Andronikos via GitHub
• Re: [svgwg] Check whether behaviour of new CSS3 units needs clarification in SVG context Amelia Bellamy-Royds via GitHub
• Re: [svgwg] 7.2 equivalent transform of an SVG viewport is mathematically wrong Claus Colloseus via GitHub
• Re: [svgwg] Check whether behaviour of new CSS3 units needs clarification in SVG context Paul LeBeau via GitHub
• [svgwg] Issue: Update content models with <audio>, <video>, <canvas> and <iframe> marked as Embedded Content chapter Nikos Andronikos via GitHub
• Closed: [svgwg] lengthAdjust="spacingAndGlyphs" is a BAD idea Nikos Andronikos via GitHub
• Re: [svgwg] SVG element names should not mix camelCase and lowercase notations Nikos Andronikos via GitHub
• Closed: [svgwg] SVG element names should not mix camelCase and lowercase notations Nikos Andronikos via GitHub
• Closed: [svgwg] Review content model and allowed attributes on all elements Nikos Andronikos via GitHub
• Re: [svgwg] Review content model and allowed attributes on all elements Nikos Andronikos via GitHub
• Re: [svgwg] Update getNumberOfChars() definition Nikos Andronikos via GitHub
• Re: [svgwg] Spec behavior of ::before and ::after within SVG text Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Spec behavior of ::before and ::after within SVG text Amelia Bellamy-Royds via GitHub
• Closed: [svgwg] Allow transforms on textPath Nikos Andronikos via GitHub
• Re: [svgwg] Allow transforms on textPath Nikos Andronikos via GitHub
• Re: [svgwg] Allow transforms on textPath Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Allow transforms on textPath Nikos Andronikos via GitHub
• Re: [svgwg] Allow transforms on textPath Nikos Andronikos via GitHub
• Closed: [svgwg] 7.2 equivalent transform of an SVG viewport is mathematically wrong Nikos Andronikos via GitHub
• Re: [svgwg] 7.2 equivalent transform of an SVG viewport is mathematically wrong Nikos Andronikos via GitHub

Thursday, 28 July 2016

• Closed: [svgwg] Mark unimplemented vector-effects options as at risk Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Update SVG DOM object initialisation to reflect promoted properties Nikos Andronikos via GitHub
• Closed: [svgwg] Update SVG DOM object initialisation to reflect promoted properties Nikos Andronikos via GitHub
• Closed: [svgwg] Can we update image's href attribute description to reference HTML51's obtain the resource algorithm? Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Can we update image's href attribute description to reference HTML51's obtain the resource algorithm? Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Add restrictions / warnings about invalid `id` values Amelia Bellamy-Royds via GitHub
• Closed: [svgwg] Add restrictions / warnings about invalid `id` values Amelia Bellamy-Royds via GitHub
• Closed: [svgwg] Specify that aria states & properties are animatable Amelia Bellamy-Royds via GitHub
• [svgwg] Add titles and lang attributes to all SVG example files Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Add titles and lang attributes to all SVG example files marked as Entire spec Amelia Bellamy-Royds via GitHub
• Closed: [svgwg] Deprecate <cursor> element Amelia Bellamy-Royds via GitHub
• Closed: [svgwg] Use a single-case name for meshGradient Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Remove redundant <dl> wrapper for the attribute table + prose block of each element Amelia Bellamy-Royds via GitHub
• Re: [svgwg] 7.2 equivalent transform of an SVG viewport is mathematically wrong Claus Colloseus via GitHub
• Closed: [svgwg] Limit pattern & gradient attributes that are inheritable using href Amelia Bellamy-Royds via GitHub
• Closed: [svgwg] Clarify effect of invalid values for width & height on <use> elements Amelia Bellamy-Royds via GitHub
• Closed: [svgwg] Define whether <use> shadow tree is interactive Amelia Bellamy-Royds via GitHub
• Closed: [svgwg] Use !important UA stylesheet rule to override display property for never-rendered elements Amelia Bellamy-Royds via GitHub
• Closed: [svgwg] Clarify what is the size of a use element if width and height are not specified Amelia Bellamy-Royds via GitHub
• Closed: [svgwg] Update href attribute descriptions to reference HTML51's obtain the resource algorithm Amelia Bellamy-Royds via GitHub
• Closed: [svgwg] Clarify meaning of context-fill & context-stroke keywords in paint definitions Amelia Bellamy-Royds via GitHub
• Closed: [svgwg] We should define the behavior of ‘use’ in terms of Web Components Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Use consistent formatting & markup for attribute definitions marked as Entire spec Amelia Bellamy-Royds via GitHub
• [svgwg] Use consistent formatting & markup for attribute definitions Amelia Bellamy-Royds via GitHub
• Re: [svgwg] 7.2 equivalent transform of an SVG viewport is mathematically wrong Nikos Andronikos via GitHub
• Re: [svgwg] Limit pattern & gradient attributes that are inheritable using href Amelia Bellamy-Royds via GitHub
• Closed: [svgwg] Define interaction of markerUnits="strokeWidth" and non-scaling-stroke Nikos Andronikos via GitHub
• Closed: [svgwg] Allow percentages in fill-opacity, stroke-opacity, & stop-opacity, to match CSS WG changes Nikos Andronikos via GitHub

Wednesday, 27 July 2016

• Re: [svgwg] Use CSS gradient rules for transitioning semi-transparent stop-colors Nikos Andronikos via GitHub
• Re: [svgwg] Use CSS gradient rules for transitioning semi-transparent stop-colors Sebastian Zartner via GitHub
• Closed: [svgwg] Use CSS gradient rules for transitioning semi-transparent stop-colors Nikos Andronikos via GitHub
• Re: [svgwg] Use CSS gradient rules for transitioning semi-transparent stop-colors Nikos Andronikos via GitHub

Tuesday, 26 July 2016

• Re: [svgwg] Update href attribute descriptions to reference HTML51's obtain the resource algorithm Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Indicate which elements need preserved state for DOM cloning marked as Entire spec Amelia Bellamy-Royds via GitHub
• [svgwg] Indicate which elements need preserved state for DOM cloning Amelia Bellamy-Royds via GitHub
• Closed: [svgwg] Define behaviour of `<stop>` if `offset` value not specified. Nikos Andronikos via GitHub
• [svgwg] Issue: Define behaviour of `<stop>` if `offset` value not specified. marked as Needs editing Nikos Andronikos via GitHub
• Re: [svgwg] Define behaviour of `<stop>` if `offset` value not specified. Nikos Andronikos via GitHub
• [svgwg] Define behaviour of `<stop>` if `offset` value not specified. Paul LeBeau via GitHub
• Closed: [svgwg] Does conditional processing mute sound playback? Nikos Andronikos via GitHub

Monday, 25 July 2016

• Re: [svgwg] Use element re-write & related changes Alex Danilo via GitHub

Saturday, 23 July 2016

• [svgwg] Issue: Update SVG WG Feedback page on w3.org to point to GitHub issues marked as Tools Amelia Bellamy-Royds via GitHub
• [svgwg] Update SVG WG Feedback page on w3.org to point to GitHub issues Amelia Bellamy-Royds via GitHub

Friday, 22 July 2016

• [svgwg] 7.2 equivalent transform of an SVG viewport is mathematically wrong Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: 7.2 equivalent transform of an SVG viewport is mathematically wrong marked as Co-ordinates chapter Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Update getNumberOfChars() definition Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Update getNumberOfChars() definition Tavmjong via GitHub
• Re: [svgwg] Update getNumberOfChars() definition Tavmjong via GitHub
• Re: [svgwg] Allow transforms on textPath Tavmjong via GitHub
• Re: [svgwg] Allow transforms on textPath Tavmjong via GitHub
• Re: [svgwg] Does conditional processing mute sound playback? Nikos Andronikos via GitHub
• Re: [svgwg] Allow transforms on textPath Nikos Andronikos via GitHub
• Re: [svgwg] Does conditional processing mute sound playback? Nikos Andronikos via GitHub
• Re: [svgwg] Use element re-write & related changes Brian Birtles via GitHub
• Re: [svgwg] Use element re-write & related changes Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Use element re-write & related changes Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Use element re-write & related changes Brian Birtles via GitHub
• Re: [svgwg] Use element re-write & related changes Alex Danilo via GitHub
• Re: [svgwg] Use element re-write & related changes Nikos Andronikos via GitHub
• [svgwg] Add a load event when tree for use element is generated? Nikos Andronikos via GitHub
• [svgwg] Issue: Add a load event when tree for use element is generated? marked as Document structure chapter Nikos Andronikos via GitHub

Thursday, 21 July 2016

• Re: [svgwg] Allow transforms on textPath Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Allow transforms on textPath Fredrik Söderqvist via GitHub
• Re: [svgwg] Allow transforms on textPath Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Allow transforms on textPath Tavmjong via GitHub
• Re: [svgwg] Allow transforms on textPath Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Update getNumberOfChars() definition Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Update getNumberOfChars() definition Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Use element re-write & related changes Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Use element re-write & related changes Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Allow stroke-dasharray/dashoffset % to be specified relative to path length Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Allow transforms on textPath Tavmjong via GitHub
• Re: [svgwg] Allow transforms on textPath Kari Pihkala via GitHub
• Re: [svgwg] Use a single-case name for meshGradient Anne van Kesteren via GitHub
• Re: [svgwg] Generalizing the utility of refx and refy by using their inverse, dx and dy Tavmjong via GitHub
• Re: [svgwg] Either make mesh a SVGGraphicsElement or make it not render to screen Tavmjong via GitHub
• Closed: [svgwg] Either make mesh a SVGGraphicsElement or make it not render to screen Tavmjong via GitHub
• Re: [svgwg] Use a single-case name for meshGradient Tavmjong via GitHub
• Re: [svgwg] Allow transforms on textPath Tavmjong via GitHub
• Re: [svgwg] Update getNumberOfChars() definition Tavmjong via GitHub
• Re: [svgwg] Define interaction of markerUnits="strokeWidth" and non-scaling-stroke Tavmjong via GitHub
• Closed: [svgwg] Need to update SVG 2 text layout algorithm Tavmjong via GitHub
• Re: [svgwg] Need to update SVG 2 text layout algorithm Tavmjong via GitHub
• Re: [svgwg] Use element re-write & related changes Tavmjong via GitHub
• Re: [svgwg] Allow stroke-dasharray/dashoffset % to be specified relative to path length Tavmjong via GitHub
• Closed: [svgwg] Use a single-case name for meshGradient Nikos Andronikos via GitHub

Wednesday, 20 July 2016

• Re: [svgwg] Allow transforms on textPath Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Add restrictions / warnings about invalid `id` values marked as Needs resolution Amelia Bellamy-Royds via GitHub
• [svgwg] Add restrictions / warnings about invalid `id` values Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Allow transforms on textPath Tavmjong via GitHub
• Re: [svgwg] Does conditional processing mute sound playback? Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Use element re-write & related changes Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Use element re-write & related changes Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Use element re-write & related changes Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Does conditional processing mute sound playback? Kari Pihkala via GitHub
• Re: [svgwg] Use element re-write & related changes Nikos Andronikos via GitHub
• Re: [svgwg] Use element re-write & related changes Nikos Andronikos via GitHub
• Re: [svgwg] Use element re-write & related changes Nikos Andronikos via GitHub
• Re: [svgwg] Use element re-write & related changes Nikos Andronikos via GitHub
• Re: [svgwg] Use element re-write & related changes Nikos Andronikos via GitHub
• Re: [svgwg] Use element re-write & related changes Nikos Andronikos via GitHub
• Re: [svgwg] Use element re-write & related changes Nikos Andronikos via GitHub
• Re: [svgwg] Use CSS gradient rules for transitioning semi-transparent stop-colors Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Use CSS gradient rules for transitioning semi-transparent stop-colors marked as agenda+ Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Make SVGAnimatedX data types extend DOMX data types wherever possible marked as agenda+ Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Does conditional processing mute sound playback? marked as agenda+ Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Use a single-case name for meshGradient Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Use a single-case name for meshGradient marked as Needs editing Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Define interaction of markerUnits="strokeWidth" and non-scaling-stroke marked as agenda+ Amelia Bellamy-Royds via GitHub

Tuesday, 19 July 2016

• [svgwg] Specify that aria states & properties are animatable Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Specify that aria states & properties are animatable marked as Needs WG input Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Change definition of percentages to match implementations Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Specify which attributes/properties are horizontal vs vertical vs other Nikos Andronikos via GitHub
• [svgwg] Issue: Specify which attributes/properties are horizontal vs vertical vs other marked as Needs editing Amelia Bellamy-Royds via GitHub
• [svgwg] Specify which attributes/properties are horizontal vs vertical vs other Amelia Bellamy-Royds via GitHub
• Closed: [svgwg] Change definition of percentages to match implementations Nikos Andronikos via GitHub
• Re: [svgwg] Allow transforms on textPath Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Allow transforms on textPath marked as Needs WG input Nikos Andronikos via GitHub
• Re: [svgwg] Allow transforms on textPath Nikos Andronikos via GitHub

Monday, 18 July 2016

• [svgwg] Allow transforms on textPath Kari Pihkala via GitHub
• Re: [svgwg] Change definition of percentages to match implementations Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Change definition of percentages to match implementations Nikos Andronikos via GitHub

Saturday, 16 July 2016

• Re: [svgwg] Rendering chapter must be more clear about the normative requirements Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Allow stroke-dasharray/dashoffset % to be specified relative to path length marked as Needs WG input Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Allow stroke-dasharray/dashoffset % to be specified relative to path length Amelia Bellamy-Royds via GitHub
• [svgwg] Change definition of percentages to match implementations Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Change definition of percentages to match implementations marked as SVG 2 Amelia Bellamy-Royds via GitHub

Friday, 15 July 2016

• Re: [svgwg] Check whether behaviour of new CSS3 units needs clarification in SVG context Sebastian Zartner via GitHub
• Re: [svgwg] Check whether behaviour of new CSS3 units needs clarification in SVG context Paul LeBeau via GitHub
• Re: [svgwg] Check whether behaviour of new CSS3 units needs clarification in SVG context Sebastian Zartner via GitHub

Thursday, 14 July 2016

• [svgwg] Synchronize SVGImageElement with HTMLImageElement Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Synchronize SVGImageElement with HTMLImageElement marked as Needs WG input Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Check whether behaviour of new CSS3 units needs clarification in SVG context marked as SVG 2 Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Check whether behaviour of new CSS3 units needs clarification in SVG context Amelia Bellamy-Royds via GitHub
• [svgwg] Check whether behaviour of new CSS3 units needs clarification in SVG context Paul LeBeau via GitHub
• Re: [svgwg] [i18n] Language fragment identifier for conditional processing Christoph Päper via GitHub

Wednesday, 13 July 2016

• [svgwg] Pull Request: Use element re-write & related changes Amelia Bellamy-Royds via GitHub
• [svgwg] Pull Request: Use element re-write & related changes Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Allow percentages in fill-opacity, stroke-opacity, & stop-opacity, to match CSS WG changes Tab Atkins Jr. via GitHub
• Re: [svgwg] Allow percentages in fill-opacity, stroke-opacity, & stop-opacity, to match CSS WG changes Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Allow percentages in fill-opacity, stroke-opacity, & stop-opacity, to match CSS WG changes marked as Paint Servers chapter Amelia Bellamy-Royds via GitHub
• [svgwg] Allow percentages in fill-opacity, stroke-opacity, & stop-opacity, to match CSS WG changes Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Define all cases for intrinsic ratio Amelia Bellamy-Royds via GitHub
• Closed: [svgwg] Define all cases for intrinsic ratio Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Update getNumberOfChars() definition Amelia Bellamy-Royds via GitHub
• Re: [svgwg] implnote.html: fix θ₁ → Δθ Waldir Pimenta via GitHub
• Re: [svgwg] implnote.html: fix θ₁ → Δθ Nikos Andronikos via GitHub
• Re: [svgwg] Update getNumberOfChars() definition Nikos Andronikos via GitHub
• Re: [svgwg] Update getNumberOfChars() definition Jarek Foksa via GitHub
• Re: [svgwg] implnote.html: fix θ₁ → Δθ Waldir Pimenta via GitHub
• Re: [svgwg] Update getNumberOfChars() definition Nikos Andronikos via GitHub
• Re: [svgwg] Define all cases for intrinsic ratio Nikos Andronikos via GitHub
• Re: [svgwg] Clarify meaning of context-fill & context-stroke keywords in paint definitions Paul LeBeau via GitHub
• Re: [svgwg] Clarify meaning of context-fill & context-stroke keywords in paint definitions Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Clarify meaning of context-fill & context-stroke keywords in paint definitions Nikos Andronikos via GitHub
• Re: [svgwg] Clarify meaning of context-fill & context-stroke keywords in paint definitions Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Clarify meaning of context-fill & context-stroke keywords in paint definitions Paul LeBeau via GitHub
• Re: [svgwg] Define context-fill & context-stroke keywords, or defer to a future spec Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Define context-fill & context-stroke keywords, or defer to a future spec Paul LeBeau via GitHub
• [svgwg] Issue: Define a vector-only processing mode marked as Needs WG input Amelia Bellamy-Royds via GitHub
• [svgwg] Define a vector-only processing mode Amelia Bellamy-Royds via GitHub
• Re: [svgwg] implnote.html: fix θ₁ → Δθ Nikos Andronikos via GitHub
• Re: [svgwg] Define context-fill & context-stroke keywords, or defer to a future spec Amelia Bellamy-Royds via GitHub
• [svgwg] Define context-fill & context-stroke keywords, or defer to a future spec Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Define context-fill & context-stroke keywords, or defer to a future spec marked as SVG 2 Amelia Bellamy-Royds via GitHub

Tuesday, 12 July 2016

• Re: [svgwg] Update getNumberOfChars() definition Jarek Foksa via GitHub
• Re: [svgwg] Define all cases for intrinsic ratio Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: What should happen regarding 1.2 Tiny features that are not mentioned in SVG2 spec? marked as Needs editing Amelia Bellamy-Royds via GitHub
• Re: [svgwg] [i18n] Language fragment identifier for conditional processing Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: [i18n] Language fragment identifier for conditional processing marked as Needs WG input Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Update getNumberOfChars() definition marked as Text chapter Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Update getNumberOfChars() definition Amelia Bellamy-Royds via GitHub
• [svgwg] Pull Request: implnote.html: fix θ₁ → Δθ Waldir Pimenta via GitHub
• [svgwg] [i18n] Language fragment identifier for conditional processing Christoph Päper via GitHub
• Re: [svgwg] Update getNumberOfChars() definition Jarek Foksa via GitHub
• [svgwg] Update getNumberOfChars() definition Jarek Foksa via GitHub
• Re: [svgwg] Define all cases for intrinsic ratio Nikos Andronikos via GitHub

Monday, 11 July 2016

• Re: [svgwg] What should happen regarding 1.2 Tiny features that are not mentioned in SVG2 spec? Nikos Andronikos via GitHub
• Re: [svgwg] Incorrect syntax for <tspan>´s attributes Nikos Andronikos via GitHub
• Re: [svgwg] What should happen regarding 1.2 Tiny features that are not mentioned in SVG2 spec? Amelia Bellamy-Royds via GitHub
• Re: [svgwg] What should happen regarding 1.2 Tiny features that are not mentioned in SVG2 spec? Paul LeBeau via GitHub
• Re: [svgwg] What should happen regarding 1.2 Tiny features that are not mentioned in SVG2 spec? Amelia Bellamy-Royds via GitHub
• Re: [svgwg] What should happen regarding 1.2 Tiny features that are not mentioned in SVG2 spec? Paul LeBeau via GitHub
• Re: [svgwg] What should happen regarding 1.2 Tiny features that are not mentioned in SVG2 spec? Amelia Bellamy-Royds via GitHub
• [svgwg] What should happen regarding 1.2 Tiny features that are not mentioned in SVG2 spec? Paul LeBeau via GitHub
• Re: [svgwg] Incorrect syntax for <tspan>´s attributes Tab Atkins Jr. via GitHub
• [svgwg] Issue: Move dataset IDL attribute from SVGElement to Element marked as Needs WG input Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Move dataset IDL attribute from SVGElement to Element Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Deprecate <cursor> element Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Deprecate <cursor> element marked as Interactivity chapter Amelia Bellamy-Royds via GitHub
• Re: [svgwg] References to editor draft specifications. Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: References to editor draft specifications. marked as Needs editing Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Define all cases for intrinsic ratio Amelia Bellamy-Royds via GitHub
• [svgwg] References to editor draft specifications. Tavmjong via GitHub
• Closed: [svgwg] Incorrect syntax for <tspan>´s attributes Nikos Andronikos via GitHub
• Re: [svgwg] Incorrect syntax for <tspan>´s attributes Nikos Andronikos via GitHub
• Re: [svgwg] Incorrect syntax for <tspan>´s attributes Nikos Andronikos via GitHub
• [svgwg] Issue: Define all cases for intrinsic ratio marked as SVG 2 Nikos Andronikos via GitHub
• [svgwg] Define all cases for intrinsic ratio Nikos Andronikos via GitHub
• [svgwg] Define script element processong model Nikos Andronikos via GitHub
• [svgwg] Issue: Define script element processong model marked as Needs WG input Nikos Andronikos via GitHub

Sunday, 10 July 2016

• Re: [svgwg] Add stub pages to SVG 2 for chapters that have been moved to separate specs Nikos Andronikos via GitHub

Saturday, 9 July 2016

• [svgwg] Issue: Add stub pages to SVG 2 for chapters that have been moved to separate specs marked as SVG 2 Amelia Bellamy-Royds via GitHub
• [svgwg] Add stub pages to SVG 2 for chapters that have been moved to separate specs Amelia Bellamy-Royds via GitHub

Friday, 8 July 2016

• [svgwg] Fix TOC styling in Editor's Drafts for specs on svgwg.org Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Fix TOC styling in Editor's Drafts for specs on svgwg.org marked as SVG Paths Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Define whether <use> shadow tree is interactive Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Define whether <use> shadow tree is interactive Philip Rogers via GitHub
• Closed: [svgwg] Restore SVGSVGElement.prototype.getElementById Nikos Andronikos via GitHub
• Re: [svgwg] Restore SVGSVGElement.prototype.getElementById Nikos Andronikos via GitHub

Thursday, 7 July 2016

• Re: [svgwg] Restore SVGSVGElement.prototype.getElementById Philip Jägenstedt via GitHub
• Re: [svgwg] Incorrect syntax for <tspan>´s attributes Sebastian Zartner via GitHub
• Re: [svgwg] Clarify effect of invalid values for width & height on <use> elements Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Clarify effect of invalid values for width & height on <use> elements Nikos Andronikos via GitHub
• [svgwg] Clarify effect of invalid values for width & height on <use> elements Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Clarify effect of invalid values for width & height on <use> elements marked as Document structure chapter Amelia Bellamy-Royds via GitHub

Wednesday, 6 July 2016

• Re: [svgwg] Incorrect syntax for <tspan>´s attributes Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Incorrect syntax for <tspan>´s attributes Sebastian Zartner via GitHub
• Re: [svgwg] Incorrect syntax for <tspan>´s attributes Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Incorrect syntax for <tspan>´s attributes marked as Needs editing Amelia Bellamy-Royds via GitHub

Tuesday, 5 July 2016

• Re: [svgwg] Use !important UA stylesheet rule to override display property for never-rendered elements Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Use !important UA stylesheet rule to override display property for never-rendered elements Nikos Andronikos via GitHub
• [svgwg] Use !important UA stylesheet rule to override display property for never-rendered elements Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Use !important UA stylesheet rule to override display property for never-rendered elements marked as Entire spec Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Restore SVGSVGElement.prototype.getElementById Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Restore SVGSVGElement.prototype.getElementById Philip Jägenstedt via GitHub
• Re: [svgwg] Restore SVGSVGElement.prototype.getElementById Paul LeBeau via GitHub
• Re: [svgwg] Restore SVGSVGElement.prototype.getElementById Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Github issues not being redirected to public-svg-issues mailing list Nikos Andronikos via GitHub
• Closed: [svgwg] Github issues not being redirected to public-svg-issues mailing list Nikos Andronikos via GitHub
• [svgwg] Incorrect syntax for <tspan>´s attributes Sebastian Zartner via GitHub
• Re: [svgwg] Restore SVGSVGElement.prototype.getElementById Anne van Kesteren via GitHub

Last message date: Friday, 29 July 2016 21:45:51 UTC