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

Monday, 30 April 2018

• [svgwg] Clarify hit testing behavior of <foreignObject> Chris Harrelson via GitHub
• Re: [svgwg] SVG2 path data coordinates are currently spec'd as integers. fuchsia via GitHub
• Re: [svgwg] Fixed path grammar Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Start using URL (instead of URI reference) CSS Meeting Bot via GitHub
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint CSS Meeting Bot via GitHub

Sunday, 29 April 2018

• Re: [svgwg] How does vector-effect=non-scaling-stroke interact with the stroke-dash* properties Dirk Schulze via GitHub

Saturday, 28 April 2018

• Re: [svgwg] Browsers do not implement transform attribute syntax as described by w3c Robert Longson via GitHub
• Closed: [svgwg] Browsers do not implement transform attribute syntax as described by w3c Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Browsers do not implement transform attribute syntax as described by w3c Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Browsers do not implement transform attribute syntax as described by w3c marked as Needs CSS WG Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Browsers do not implement transform attribute syntax as described by w3c Amelia Bellamy-Royds via GitHub
• [svgwg] Browsers do not implement transform attribute syntax as described by w3c Robert Longson via GitHub

Friday, 27 April 2018

• Re: [svgwg] How does vector-effect=non-scaling-stroke interact with the stroke-dash* properties Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: What should happen if you try to set an out of range value on an enum in the DOM marked as Agenda+ Chris Lilley via GitHub
• [svgwg] Issue: dur attribute should permit leading . marked as Agenda+ Chris Lilley via GitHub
• Re: [svgwg] How does vector-effect=non-scaling-stroke interact with the stroke-dash* properties Ulrich-Matthias Schäfer via GitHub
• Re: [svgwg] Add or update dfns for definitions David Storey via GitHub
• [svgwg] Pull Request: Add or update dfns for definitions David Storey via GitHub

Tuesday, 24 April 2018

• [svgwg] Issue: Do we really need not to reflect additional enum values in SVG 2 marked as SVG Markers Dirk Schulze via GitHub
• Re: [svgwg] Do we really need not to reflect additional enum values in SVG 2 Dirk Schulze via GitHub
• Re: [svgwg] Do we really need not to reflect additional enum values in SVG 2 Robert Longson via GitHub
• Re: [svgwg] Use <dfn> for definitions David Storey via GitHub
• Re: [svgwg] Use <dfn> for definitions Dirk Schulze via GitHub

Monday, 23 April 2018

• Re: [svgwg] Use <dfn> for definitions Tab Atkins Jr. via GitHub
• Re: [svgwg] Do we really need not to reflect additional enum values in SVG 2 Robert Longson via GitHub
• Re: [svgwg] Bounding box algorithm is not precise Paul LeBeau via GitHub
• Re: [svgwg] Do we really need not to reflect additional enum values in SVG 2 Dirk Schulze via GitHub
• Re: [svgwg] Bounding box algorithm is not precise Dirk Schulze via GitHub
• [svgwg] Do we really need not to reflect additional enum values in SVG 2 Robert Longson via GitHub
• Re: [svgwg] Bounding box algorithm is not precise Paul LeBeau via GitHub
• [svgwg] What should happen if you try to set an out of range value on an enum in the DOM Robert Longson via GitHub
• Re: [svgwg] Bounding box algorithm is not precise Dirk Schulze via GitHub

Sunday, 22 April 2018

• Re: [svgwg] Bounding box algorithm is not precise Paul LeBeau via GitHub
• Re: [svgwg] Bounding box algorithm is not precise Dirk Schulze via GitHub
• [svgwg] Issue: Bounding box algorithm is not precise marked as Co-ordinates chapter Dirk Schulze via GitHub
• [svgwg] Bounding box algorithm is not precise Dirk Schulze via GitHub
• Re: [svgwg] Rename SVGBoundingBoxOptions to SVGBoundingBoxOptionsInit Dirk Schulze via GitHub
• Re: [svgwg] Rename SVGBoundingBoxOptions to SVGBoundingBoxOptionsInit David Storey via GitHub
• Re: [svgwg] Rename SVGBoundingBoxOptions to SVGBoundingBoxOptionsInit David Storey via GitHub
• Re: [svgwg] context-value UA rules for OpenType are giving unexpected rendering / compat problems Amelia Bellamy-Royds via GitHub

Saturday, 21 April 2018

• Re: [svgwg] context-value UA rules for OpenType are giving unexpected rendering / compat problems Xidorn Quan via GitHub
• Re: [svgwg] context-value UA rules for OpenType are giving unexpected rendering / compat problems Amelia Bellamy-Royds via GitHub
• [svgwg] context-value UA rules for OpenType are giving unexpected rendering / compat problems Emilio Cobos Álvarez via GitHub
• [svgwg] Issue: Start using URL (instead of URI reference) marked as Needs editing Dirk Schulze via GitHub
• Re: [svgwg] Start using URL (instead of URI reference) Dirk Schulze via GitHub
• Re: [svgwg] Use <dfn> for definitions Peter Linss via GitHub
• [svgwg] Start using URL (instead of URI reference) Anne van Kesteren via GitHub
• Re: [svgwg] Use <dfn> for definitions Dirk Schulze via GitHub
• Re: [svgwg] Fixed path grammar Amelia Bellamy-Royds via GitHub
• Re: [svgwg] SVG2 path data coordinates are currently spec'd as integers. Amelia Bellamy-Royds via GitHub
• Re: [svgwg] SVG2 path data coordinates are currently spec'd as integers. fuchsia via GitHub
• [svgwg] new commits pushed by dstorey David Storey via GitHub
• [svgwg] Merged Pull Request: Keep the linting minions happy David Storey via GitHub
• Re: [svgwg] Use <dfn> for definitions David Storey via GitHub
• Re: [svgwg] Use <dfn> for definitions Peter Linss via GitHub
• Re: [svgwg] Use <dfn> for definitions Dirk Schulze via GitHub
• [svgwg] Issue: Rename SVGBoundingBoxOptions to SVGBoundingBoxOptionsInit marked as Basic Data Types and Interfaces chapter Dirk Schulze via GitHub
• [svgwg] Rename SVGBoundingBoxOptions to SVGBoundingBoxOptionsInit Dirk Schulze via GitHub
• Re: [svgwg] Clarify relation of isPointInFill and pointer-events Dirk Schulze via GitHub

Friday, 20 April 2018

• Re: [svgwg] Add DocumentAndElementEventHandlers David Storey via GitHub
• [svgwg] Pull Request: Keep the linting minions happy David Storey via GitHub
• Closed: [svgwg] Move dataset & other shared IDL attributes from SVGElement to HTMLOrSVGElement David Storey via GitHub
• [svgwg] new commits pushed by dstorey David Storey via GitHub
• [svgwg] Merged Pull Request: Add HTMLOrSVGElement mixn David Storey via GitHub
• Re: [svgwg] Clarify relation of isPointInFill and pointer-events Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Use <dfn> for definitions David Storey via GitHub
• [svgwg] Use <dfn> for definitions fantasai via GitHub
• Re: [svgwg] Clarify relation of isPointInFill and pointer-events Dirk Schulze via GitHub
• [svgwg] Issue: Clarify relation of isPointInFill and pointer-events marked as Agenda+ Dirk Schulze via GitHub
• Re: [svgwg] Clarify relation of isPointInFill and pointer-events Dirk Schulze via GitHub
• [svgwg] Clarify relation of isPointInFill and pointer-events Dirk Schulze via GitHub

Thursday, 19 April 2018

• Re: [svgwg] Add DocumentAndElementEventHandlers David Storey via GitHub
• Re: [svgwg] Add HTMLOrSVGElement mixn David Storey via GitHub
• Re: [svgwg] Add HTMLOrSVGElement mixn Dirk Schulze via GitHub
• Re: [svgwg] Add HTMLOrSVGElement mixn Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Add HTMLOrSVGElement mixn Tobie Langel via GitHub
• Re: [svgwg] Add HTMLOrSVGElement mixn David Storey via GitHub
• Re: [svgwg] Add HTMLOrSVGElement mixn Tobie Langel via GitHub
• Re: [svgwg] Add HTMLOrSVGElement mixn Dirk Schulze via GitHub
• Re: [svgwg] Add HTMLOrSVGElement mixn David Storey via GitHub
• Re: [svgwg] Add HTMLOrSVGElement mixn David Storey via GitHub
• Re: [svgwg] Add HTMLOrSVGElement mixn Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Add HTMLOrSVGElement mixn David Storey via GitHub

Wednesday, 18 April 2018

• Re: [svgwg] Remove support for segment-completing close path Dirk Schulze via GitHub
• Re: [svgwg] Remove support for segment-completing close path Dirk Schulze via GitHub
• [svgwg] Pull Request: Add HTMLOrSVGElement mixn David Storey via GitHub

Tuesday, 17 April 2018

• Re: [svgwg] Use DOMPointInit argument for getCharNumAtPosition. #389 Dirk Schulze via GitHub
• Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible David Storey via GitHub
• Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible Amelia Bellamy-Royds via GitHub

Monday, 16 April 2018

• Re: [svgwg] Update SVGScriptElement and SVGImageElement to use src? David Storey via GitHub

Sunday, 15 April 2018

• Re: [svgwg] Update SVGScriptElement and SVGImageElement to use src? Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Update SVGScriptElement and SVGImageElement to use src? Martin Janecke via GitHub
• [svgwg] Pull Request: Use DOMPointInit argument for getCharNumAtPosition. #389 Dirk Schulze via GitHub

Friday, 13 April 2018

• Re: [svgwg] Add DocumentAndElementEventHandlers Amelia Bellamy-Royds via GitHub

Thursday, 12 April 2018

• Re: [svgwg] Deprecate type attribute on SVGStyleElement? David Storey via GitHub
• Re: [svgwg] Add DocumentAndElementEventHandlers David Storey via GitHub
• [svgwg] Pull Request: Add DocumentAndElementEventHandlers David Storey via GitHub
• Re: [svgwg] Do we need to replace DOMStringMap? Amelia Bellamy-Royds via GitHub
• Closed: [svgwg] Do we need to replace DOMStringMap? Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Remove "style attributes" from all element definitions Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Remove "style attributes" from all element definitions marked as SVG Core Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Deprecate type attribute on SVGStyleElement? Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Do we need to replace DOMStringMap? David Storey via GitHub
• Re: [svgwg] Do we need to replace DOMStringMap? Dirk Schulze via GitHub
• Re: [svgwg] Do we need to replace DOMStringMap? 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 Amelia Bellamy-Royds 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 Paul LeBeau 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 Paul LeBeau via GitHub
• [svgwg] Do we need to replace DOMStringMap? Dirk Schulze via GitHub
• Closed: [svgwg] Update WebIDL definition(s) to use new mixin syntax Dirk Schulze via GitHub
• [svgwg] new commits pushed by dirkschulze Dirk Schulze via GitHub
• [svgwg] Merged Pull Request: Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 Dirk Schulze 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 Dirk Schulze via GitHub
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint Paul LeBeau via GitHub
• Re: [svgwg] Deprecate type attribute on SVGStyleElement? Dirk Schulze via GitHub
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint Dirk Schulze 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 Dirk Schulze via GitHub
• [svgwg] Deprecate type attribute on SVGStyleElement? David Storey via GitHub
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint Tab Atkins Jr. via GitHub
• [svgwg] Issue: Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint marked as Agenda+ Dirk Schulze via GitHub
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint Dirk Schulze via GitHub
• [svgwg] Update SVGScriptElement and SVGImageElement to use src? David Storey via GitHub
• Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible Robert Longson via GitHub
• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 Dirk Schulze via GitHub
• Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible Travis Leithead via GitHub

Wednesday, 11 April 2018

• Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible David Storey via GitHub
• Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible David Storey via GitHub
• [svgwg] new commits pushed by dirkschulze Dirk Schulze via GitHub
• [svgwg] Merged Pull Request: Clarify patternTransform/linearTransform presentation attriute behavi… Dirk Schulze via GitHub

Tuesday, 10 April 2018

• Re: [svgwg] SVG MIME Type (image/svg+xml) is misleading to developers Teoh Han Hui via GitHub
• Re: [svgwg] Update SVGAElement to match attributes on HTMLAnchorElement David Storey via GitHub
• [svgwg] Pull Request: Update SVGAElement to match attributes on HTMLAnchorElement David Storey via GitHub
• [svgwg] Merged Pull Request: Fixes #407 copy-pasto in viewBox definition David Storey via GitHub
• Closed: [svgwg] Typo in viewBox attribute type definition David Storey via GitHub
• [svgwg] new commits pushed by dstorey David Storey via GitHub

Monday, 9 April 2018

• [svgwg] Pull Request: Fixes #407 copy-pasto in viewBox definition David Storey via GitHub
• Re: [svgwg] Cut down number of categories Amelia Bellamy-Royds via GitHub

Sunday, 8 April 2018

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

Tuesday, 3 April 2018

• Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible David Storey via GitHub
• Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible David Storey via GitHub
• Re: [svgwg] SVGAElement implements two conflicting interfaces David Storey via GitHub
• Re: [svgwg] Remove support for segment-completing close path Eric Willigers via GitHub
• Re: [svgwg] Convert SVG linking reftests to .svg files Cameron McCormack via GitHub

Monday, 2 April 2018

• Closed: [svgwg] "mode" of a shadow root which <use> element uses is unclear Amelia Bellamy-Royds via GitHub
• Re: [svgwg] "mode" of a shadow root which <use> element uses is unclear Amelia Bellamy-Royds via GitHub
• Re: [svgwg] Revisions to sentence on focusable elements CSS Meeting Bot via GitHub
• [svgwg] Merged Pull Request: Revisions to sentence on focusable elements Bogdan Brinza via GitHub
• Re: [svgwg] Change SVGMeshElement to derive from SVGGraphicsElement CSS Meeting Bot via GitHub
• [svgwg] Closed Pull Request: Change SVGMeshElement to derive from SVGGraphicsElement Bogdan Brinza via GitHub
• Re: [svgwg] Remove support for segment-completing close path CSS Meeting Bot via GitHub
• Re: [svgwg] Fixed path grammar CSS Meeting Bot via GitHub
• Re: [svgwg] Add text-transform property to the list of required CSS properties CSS Meeting Bot via GitHub
• [svgwg] Closed Pull Request: Add text-transform property to the list of required CSS properties Bogdan Brinza via GitHub
• Re: [svgwg] Add text-transform property to the list of required CSS properties Bogdan Brinza via GitHub
• Re: [svgwg] 'd' presentation attribute: use path() function CSS Meeting Bot via GitHub
• Re: [svgwg] Cut down number of categories Jarek Foksa via GitHub
• [svgwg] Typo in viewBox attribute type definition Jarek Foksa via GitHub
• [svgwg] Wrong description of percentage units Jarek Foksa via GitHub

Sunday, 1 April 2018

• Re: [svgwg] Wrong description of "visibility" property Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Wrong description of "visibility" property marked as Document structure chapter Amelia Bellamy-Royds via GitHub
• [svgwg] Wrong description of "visibility" property Jarek Foksa via GitHub
• Closed: [svgwg] Remove "text content child element" category Jarek Foksa via GitHub
• Re: [svgwg] Remove "text content child element" category Jarek Foksa via GitHub
• Re: [svgwg] Replace <opacity-value> with <alpha-value> Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: Replace <opacity-value> with <alpha-value> marked as SVG Core Amelia Bellamy-Royds via GitHub
• [svgwg] Issue: The computed value of fill-opacity and stroke-opacity should never be a percentage marked as SVG Core Amelia Bellamy-Royds via GitHub
• Re: [svgwg] The computed value of fill-opacity and stroke-opacity should never be a percentage Amelia Bellamy-Royds via GitHub
• Re: [svgwg] The computed value of fill-opacity and stroke-opacity should never be a percentage Robert Longson via GitHub
• [svgwg] Remove "style attributes" from all element definitions Jarek Foksa via GitHub
• [svgwg] Replace <opacity-value> with <alpha-value> Jarek Foksa via GitHub
• [svgwg] The computed value of fill-opacity stroke-opacity should never be a percentage Jarek Foksa via GitHub
• Re: [svgwg] Add <a> to "text content element" category Jarek Foksa via GitHub
• [svgwg] Allow more properties to be applied on <a> inside <text> Jarek Foksa via GitHub
• Re: [svgwg] Add <a> to "text content element" category Robert Longson via GitHub
• Re: [svgwg] Add <a> to "text content element" category Jarek Foksa via GitHub
• Closed: [svgwg] Add <a> to "text content element" category Jarek Foksa via GitHub
• Re: [svgwg] Add <a> to "text content element" category Robert Longson via GitHub

Last message date: Monday, 30 April 2018 21:50:27 UTC