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

Amelia Bellamy-Royds via GitHub

• Re: [svgwg] Fixed path grammar (Monday, 30 April)
• Closed: [svgwg] Browsers do not implement transform attribute syntax as described by w3c (Saturday, 28 April)
• Re: [svgwg] Browsers do not implement transform attribute syntax as described by w3c (Saturday, 28 April)
• [svgwg] Issue: Browsers do not implement transform attribute syntax as described by w3c marked as Needs CSS WG (Saturday, 28 April)
• Re: [svgwg] Browsers do not implement transform attribute syntax as described by w3c (Saturday, 28 April)
• Re: [svgwg] How does vector-effect=non-scaling-stroke interact with the stroke-dash* properties (Friday, 27 April)
• Re: [svgwg] context-value UA rules for OpenType are giving unexpected rendering / compat problems (Sunday, 22 April)
• Re: [svgwg] context-value UA rules for OpenType are giving unexpected rendering / compat problems (Saturday, 21 April)
• Re: [svgwg] Fixed path grammar (Saturday, 21 April)
• Re: [svgwg] SVG2 path data coordinates are currently spec'd as integers. (Saturday, 21 April)
• Re: [svgwg] Clarify relation of isPointInFill and pointer-events (Friday, 20 April)
• Re: [svgwg] Add HTMLOrSVGElement mixn (Thursday, 19 April)
• Re: [svgwg] Add HTMLOrSVGElement mixn (Thursday, 19 April)
• Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible (Tuesday, 17 April)
• Re: [svgwg] Update SVGScriptElement and SVGImageElement to use src? (Sunday, 15 April)
• Re: [svgwg] Add DocumentAndElementEventHandlers (Friday, 13 April)
• Re: [svgwg] Do we need to replace DOMStringMap? (Thursday, 12 April)
• Closed: [svgwg] Do we need to replace DOMStringMap? (Thursday, 12 April)
• Re: [svgwg] Remove "style attributes" from all element definitions (Thursday, 12 April)
• [svgwg] Issue: Remove "style attributes" from all element definitions marked as SVG Core (Thursday, 12 April)
• Re: [svgwg] Deprecate type attribute on SVGStyleElement? (Thursday, 12 April)
• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 (Thursday, 12 April)
• Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible (Wednesday, 11 April)
• Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible (Wednesday, 11 April)
• Re: [svgwg] Cut down number of categories (Monday, 9 April)
• Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible (Tuesday, 3 April)
• Closed: [svgwg] "mode" of a shadow root which <use> element uses is unclear (Monday, 2 April)
• Re: [svgwg] "mode" of a shadow root which <use> element uses is unclear (Monday, 2 April)
• Re: [svgwg] Wrong description of "visibility" property (Sunday, 1 April)
• [svgwg] Issue: Wrong description of "visibility" property marked as Document structure chapter (Sunday, 1 April)
• Re: [svgwg] Replace <opacity-value> with <alpha-value> (Sunday, 1 April)
• [svgwg] Issue: Replace <opacity-value> with <alpha-value> marked as SVG Core (Sunday, 1 April)
• [svgwg] Issue: The computed value of fill-opacity and stroke-opacity should never be a percentage marked as SVG Core (Sunday, 1 April)
• Re: [svgwg] The computed value of fill-opacity and stroke-opacity should never be a percentage (Sunday, 1 April)

Anne van Kesteren via GitHub

• [svgwg] Start using URL (instead of URI reference) (Saturday, 21 April)

Bogdan Brinza via GitHub

• [svgwg] Merged Pull Request: Revisions to sentence on focusable elements (Monday, 2 April)
• [svgwg] Closed Pull Request: Change SVGMeshElement to derive from SVGGraphicsElement (Monday, 2 April)
• [svgwg] Closed Pull Request: Add text-transform property to the list of required CSS properties (Monday, 2 April)
• Re: [svgwg] Add text-transform property to the list of required CSS properties (Monday, 2 April)

Cameron McCormack via GitHub

• Re: [svgwg] Convert SVG linking reftests to .svg files (Tuesday, 3 April)

Chris Harrelson via GitHub

• [svgwg] Clarify hit testing behavior of <foreignObject> (Monday, 30 April)

Chris Lilley 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+ (Friday, 27 April)
• [svgwg] Issue: dur attribute should permit leading . marked as Agenda+ (Friday, 27 April)

CSS Meeting Bot via GitHub

• Re: [svgwg] Start using URL (instead of URI reference) (Monday, 30 April)
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint (Monday, 30 April)
• Re: [svgwg] Revisions to sentence on focusable elements (Monday, 2 April)
• Re: [svgwg] Change SVGMeshElement to derive from SVGGraphicsElement (Monday, 2 April)
• Re: [svgwg] Remove support for segment-completing close path (Monday, 2 April)
• Re: [svgwg] Fixed path grammar (Monday, 2 April)
• Re: [svgwg] Add text-transform property to the list of required CSS properties (Monday, 2 April)
• Re: [svgwg] 'd' presentation attribute: use path() function (Monday, 2 April)

David Storey via GitHub

• Re: [svgwg] Add or update dfns for definitions (Friday, 27 April)
• [svgwg] Pull Request: Add or update dfns for definitions (Friday, 27 April)
• Re: [svgwg] Use <dfn> for definitions (Tuesday, 24 April)
• Re: [svgwg] Rename SVGBoundingBoxOptions to SVGBoundingBoxOptionsInit (Sunday, 22 April)
• Re: [svgwg] Rename SVGBoundingBoxOptions to SVGBoundingBoxOptionsInit (Sunday, 22 April)
• [svgwg] new commits pushed by dstorey (Saturday, 21 April)
• [svgwg] Merged Pull Request: Keep the linting minions happy (Saturday, 21 April)
• Re: [svgwg] Use <dfn> for definitions (Saturday, 21 April)
• Re: [svgwg] Add DocumentAndElementEventHandlers (Friday, 20 April)
• [svgwg] Pull Request: Keep the linting minions happy (Friday, 20 April)
• [svgwg] new commits pushed by dstorey (Friday, 20 April)
• Closed: [svgwg] Move dataset & other shared IDL attributes from SVGElement to HTMLOrSVGElement (Friday, 20 April)
• [svgwg] Merged Pull Request: Add HTMLOrSVGElement mixn (Friday, 20 April)
• Re: [svgwg] Use <dfn> for definitions (Friday, 20 April)
• Re: [svgwg] Add DocumentAndElementEventHandlers (Thursday, 19 April)
• Re: [svgwg] Add HTMLOrSVGElement mixn (Thursday, 19 April)
• Re: [svgwg] Add HTMLOrSVGElement mixn (Thursday, 19 April)
• Re: [svgwg] Add HTMLOrSVGElement mixn (Thursday, 19 April)
• Re: [svgwg] Add HTMLOrSVGElement mixn (Thursday, 19 April)
• Re: [svgwg] Add HTMLOrSVGElement mixn (Thursday, 19 April)
• [svgwg] Pull Request: Add HTMLOrSVGElement mixn (Wednesday, 18 April)
• Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible (Tuesday, 17 April)
• Re: [svgwg] Update SVGScriptElement and SVGImageElement to use src? (Monday, 16 April)
• Re: [svgwg] Deprecate type attribute on SVGStyleElement? (Thursday, 12 April)
• Re: [svgwg] Add DocumentAndElementEventHandlers (Thursday, 12 April)
• [svgwg] Pull Request: Add DocumentAndElementEventHandlers (Thursday, 12 April)
• Re: [svgwg] Do we need to replace DOMStringMap? (Thursday, 12 April)
• Re: [svgwg] Do we need to replace DOMStringMap? (Thursday, 12 April)
• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 (Thursday, 12 April)
• [svgwg] Deprecate type attribute on SVGStyleElement? (Thursday, 12 April)
• [svgwg] Update SVGScriptElement and SVGImageElement to use src? (Thursday, 12 April)
• Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible (Wednesday, 11 April)
• Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible (Wednesday, 11 April)
• Re: [svgwg] Update SVGAElement to match attributes on HTMLAnchorElement (Tuesday, 10 April)
• [svgwg] Pull Request: Update SVGAElement to match attributes on HTMLAnchorElement (Tuesday, 10 April)
• [svgwg] Merged Pull Request: Fixes #407 copy-pasto in viewBox definition (Tuesday, 10 April)
• Closed: [svgwg] Typo in viewBox attribute type definition (Tuesday, 10 April)
• [svgwg] new commits pushed by dstorey (Tuesday, 10 April)
• [svgwg] Pull Request: Fixes #407 copy-pasto in viewBox definition (Monday, 9 April)
• Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible (Tuesday, 3 April)
• Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible (Tuesday, 3 April)
• Re: [svgwg] SVGAElement implements two conflicting interfaces (Tuesday, 3 April)

Dirk Schulze via GitHub

• Re: [svgwg] How does vector-effect=non-scaling-stroke interact with the stroke-dash* properties (Sunday, 29 April)
• [svgwg] Issue: Do we really need not to reflect additional enum values in SVG 2 marked as SVG Markers (Tuesday, 24 April)
• Re: [svgwg] Do we really need not to reflect additional enum values in SVG 2 (Tuesday, 24 April)
• Re: [svgwg] Use <dfn> for definitions (Tuesday, 24 April)
• Re: [svgwg] Do we really need not to reflect additional enum values in SVG 2 (Monday, 23 April)
• Re: [svgwg] Bounding box algorithm is not precise (Monday, 23 April)
• Re: [svgwg] Bounding box algorithm is not precise (Monday, 23 April)
• Re: [svgwg] Bounding box algorithm is not precise (Sunday, 22 April)
• [svgwg] Issue: Bounding box algorithm is not precise marked as Co-ordinates chapter (Sunday, 22 April)
• [svgwg] Bounding box algorithm is not precise (Sunday, 22 April)
• Re: [svgwg] Rename SVGBoundingBoxOptions to SVGBoundingBoxOptionsInit (Sunday, 22 April)
• [svgwg] Issue: Start using URL (instead of URI reference) marked as Needs editing (Saturday, 21 April)
• Re: [svgwg] Start using URL (instead of URI reference) (Saturday, 21 April)
• Re: [svgwg] Use <dfn> for definitions (Saturday, 21 April)
• Re: [svgwg] Use <dfn> for definitions (Saturday, 21 April)
• [svgwg] Issue: Rename SVGBoundingBoxOptions to SVGBoundingBoxOptionsInit marked as Basic Data Types and Interfaces chapter (Saturday, 21 April)
• [svgwg] Rename SVGBoundingBoxOptions to SVGBoundingBoxOptionsInit (Saturday, 21 April)
• Re: [svgwg] Clarify relation of isPointInFill and pointer-events (Saturday, 21 April)
• Re: [svgwg] Clarify relation of isPointInFill and pointer-events (Friday, 20 April)
• [svgwg] Issue: Clarify relation of isPointInFill and pointer-events marked as Agenda+ (Friday, 20 April)
• Re: [svgwg] Clarify relation of isPointInFill and pointer-events (Friday, 20 April)
• [svgwg] Clarify relation of isPointInFill and pointer-events (Friday, 20 April)
• Re: [svgwg] Add HTMLOrSVGElement mixn (Thursday, 19 April)
• Re: [svgwg] Add HTMLOrSVGElement mixn (Thursday, 19 April)
• Re: [svgwg] Remove support for segment-completing close path (Wednesday, 18 April)
• Re: [svgwg] Remove support for segment-completing close path (Wednesday, 18 April)
• Re: [svgwg] Use DOMPointInit argument for getCharNumAtPosition. #389 (Tuesday, 17 April)
• [svgwg] Pull Request: Use DOMPointInit argument for getCharNumAtPosition. #389 (Sunday, 15 April)
• Re: [svgwg] Do we need to replace DOMStringMap? (Thursday, 12 April)
• [svgwg] Do we need to replace DOMStringMap? (Thursday, 12 April)
• Closed: [svgwg] Update WebIDL definition(s) to use new mixin syntax (Thursday, 12 April)
• [svgwg] new commits pushed by dirkschulze (Thursday, 12 April)
• [svgwg] Merged Pull Request: Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 (Thursday, 12 April)
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint (Thursday, 12 April)
• Re: [svgwg] Deprecate type attribute on SVGStyleElement? (Thursday, 12 April)
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint (Thursday, 12 April)
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint (Thursday, 12 April)
• [svgwg] Issue: Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint marked as Agenda+ (Thursday, 12 April)
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint (Thursday, 12 April)
• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 (Thursday, 12 April)
• [svgwg] new commits pushed by dirkschulze (Wednesday, 11 April)
• [svgwg] Merged Pull Request: Clarify patternTransform/linearTransform presentation attriute behavi… (Wednesday, 11 April)

Emilio Cobos Álvarez via GitHub

• [svgwg] context-value UA rules for OpenType are giving unexpected rendering / compat problems (Saturday, 21 April)

Eric Willigers via GitHub

• Re: [svgwg] Remove support for segment-completing close path (Tuesday, 3 April)

fantasai via GitHub

• [svgwg] Use <dfn> for definitions (Friday, 20 April)

fuchsia via GitHub

• Re: [svgwg] SVG2 path data coordinates are currently spec'd as integers. (Monday, 30 April)
• Re: [svgwg] SVG2 path data coordinates are currently spec'd as integers. (Saturday, 21 April)

Jarek Foksa via GitHub

• Re: [svgwg] Cut down number of categories (Monday, 2 April)
• [svgwg] Typo in viewBox attribute type definition (Monday, 2 April)
• [svgwg] Wrong description of percentage units (Monday, 2 April)
• [svgwg] Wrong description of "visibility" property (Sunday, 1 April)
• Closed: [svgwg] Remove "text content child element" category (Sunday, 1 April)
• Re: [svgwg] Remove "text content child element" category (Sunday, 1 April)
• [svgwg] Remove "style attributes" from all element definitions (Sunday, 1 April)
• [svgwg] Replace <opacity-value> with <alpha-value> (Sunday, 1 April)
• [svgwg] The computed value of fill-opacity stroke-opacity should never be a percentage (Sunday, 1 April)
• Re: [svgwg] Add <a> to "text content element" category (Sunday, 1 April)
• [svgwg] Allow more properties to be applied on <a> inside <text> (Sunday, 1 April)
• Re: [svgwg] Add <a> to "text content element" category (Sunday, 1 April)
• Closed: [svgwg] Add <a> to "text content element" category (Sunday, 1 April)

Martin Janecke via GitHub

• Re: [svgwg] Update SVGScriptElement and SVGImageElement to use src? (Sunday, 15 April)

Paul LeBeau via GitHub

• Re: [svgwg] Bounding box algorithm is not precise (Monday, 23 April)
• Re: [svgwg] Bounding box algorithm is not precise (Monday, 23 April)
• Re: [svgwg] Bounding box algorithm is not precise (Sunday, 22 April)
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint (Thursday, 12 April)
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint (Thursday, 12 April)
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint (Thursday, 12 April)

Peter Linss via GitHub

• Re: [svgwg] Use <dfn> for definitions (Saturday, 21 April)
• Re: [svgwg] Use <dfn> for definitions (Saturday, 21 April)

Robert Longson via GitHub

• Re: [svgwg] Browsers do not implement transform attribute syntax as described by w3c (Saturday, 28 April)
• [svgwg] Browsers do not implement transform attribute syntax as described by w3c (Saturday, 28 April)
• Re: [svgwg] Do we really need not to reflect additional enum values in SVG 2 (Tuesday, 24 April)
• Re: [svgwg] Do we really need not to reflect additional enum values in SVG 2 (Monday, 23 April)
• [svgwg] Do we really need not to reflect additional enum values in SVG 2 (Monday, 23 April)
• [svgwg] What should happen if you try to set an out of range value on an enum in the DOM (Monday, 23 April)
• Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible (Thursday, 12 April)
• Re: [svgwg] The computed value of fill-opacity and stroke-opacity should never be a percentage (Sunday, 1 April)
• Re: [svgwg] Add <a> to "text content element" category (Sunday, 1 April)
• Re: [svgwg] Add <a> to "text content element" category (Sunday, 1 April)

Tab Atkins Jr. via GitHub

• Re: [svgwg] Use <dfn> for definitions (Monday, 23 April)
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint (Thursday, 12 April)
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint (Thursday, 12 April)
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint (Thursday, 12 April)
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint (Thursday, 12 April)
• Re: [svgwg] Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint (Thursday, 12 April)

Teoh Han Hui via GitHub

• Re: [svgwg] SVG MIME Type (image/svg+xml) is misleading to developers (Tuesday, 10 April)

Tobie Langel via GitHub

• Re: [svgwg] Add HTMLOrSVGElement mixn (Thursday, 19 April)
• Re: [svgwg] Add HTMLOrSVGElement mixn (Thursday, 19 April)
• Re: [svgwg] Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 (Sunday, 8 April)

Travis Leithead via GitHub

• Re: [svgwg] Make SVGAnimatedX data types extend DOMX data types wherever possible (Thursday, 12 April)

Ulrich-Matthias Schäfer via GitHub

• Re: [svgwg] How does vector-effect=non-scaling-stroke interact with the stroke-dash* properties (Friday, 27 April)

Xidorn Quan via GitHub

• Re: [svgwg] context-value UA rules for OpenType are giving unexpected rendering / compat problems (Saturday, 21 April)

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