Weekly github digest (svgwg, svg-aam, fxtf-drafts, graphics-aam, graphics-aria)

Issues
------
* w3c/svgwg (+3/-1/💬19)
  3 issues created:
  - pointer-events auto (by ewilligers)
    https://github.com/w3c/svgwg/issues/574 [Interactivity chapter] 
  - pointer-events bounding-box (by ewilligers)
    https://github.com/w3c/svgwg/issues/573 
  - Proposal for addition of new commands in the Path Data language (by ratishphilip)
    https://github.com/w3c/svgwg/issues/572 

  8 issues received 19 new comments:
  - #537 Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes. (10 by r12a, litherum, fantasai, AmeliaBR)
    https://github.com/w3c/svgwg/issues/537 [Needs editing] [Needs tests] [Text chapter] [i18n-tracking] 
  - #572 Proposal for addition of new commands in the Path Data language (2 by litherum, ratishphilip)
    https://github.com/w3c/svgwg/issues/572 
  - #574 pointer-events auto (2 by ewilligers, css-meeting-bot)
    https://github.com/w3c/svgwg/issues/574 [Interactivity chapter] 
  - #553 Z-axis (1 by ewilligers)
    https://github.com/w3c/svgwg/issues/553 [Rendering Model chapter] [SVG Core] 
  - #559 SVGGeometry.prototype.isPointInStroke vs. vector-effects (1 by css-meeting-bot)
    https://github.com/w3c/svgwg/issues/559 [Basic Data Types and Interfaces chapter] [Needs editing] [Painting chapter] [SVG Core] 
  - #306 Since vector-effect options other than non-scaling-stroke already have multiple implementations, is the "at risk" flag valid? (1 by css-meeting-bot)
    https://github.com/w3c/svgwg/issues/306 [Entire spec] [Has tests] [Needs editing] 
  - #469 Define how new sizing keywords are resolved for SVG width and height geometry properties (1 by css-meeting-bot)
    https://github.com/w3c/svgwg/issues/469 [Geometry Properties chapter] [SVG Core] 
  - #373 Add decode() and decoding attribute to SVGImageElement (1 by css-meeting-bot)
    https://github.com/w3c/svgwg/issues/373 [HTML Consistency] 

  1 issues closed:
  - typo: Elmenent https://github.com/w3c/svgwg/issues/569 [Needs editing] 

* w3c/fxtf-drafts (+1/-1/💬18)
  1 issues created:
  - [css-transforms-2] Serialize `scale` if we only use one number (by BorisChiou)
    https://github.com/w3c/fxtf-drafts/issues/313 

  2 issues received 18 new comments:
  - #313 [css-transforms-2] How to serialize `scale` if we only use one number? (16 by ewilligers, tabatkins, svgeesus, heycam, BorisChiou)
    https://github.com/w3c/fxtf-drafts/issues/313 
  - #310 [filter-effects-2] Publish FPWD (2 by ewilligers, svgeesus)
    https://github.com/w3c/fxtf-drafts/issues/310 [Agenda+] [filter-effects-2] 

  1 issues closed:
  - [css-transforms-2] How to serialize `scale` if we only use one number? https://github.com/w3c/fxtf-drafts/issues/313 



Pull requests
-------------
* w3c/svgwg (+1/-0/💬3)
  1 pull requests submitted:
  - [interactivity] pointer-events auto (by ewilligers)
    https://github.com/w3c/svgwg/pull/575 

  1 pull requests received 3 new comments:
  - #374 'd' presentation attribute: use path() function (3 by ewilligers, css-meeting-bot, Tavmjong)
    https://github.com/w3c/svgwg/pull/374 [Agenda+] [Basic shapes chapter] [Geometry Properties chapter] [Needs WG input] 

* w3c/fxtf-drafts (+1/-1/💬0)
  1 pull requests submitted:
  - [motion] reverse does not appear in computed value (by ewilligers)
    https://github.com/w3c/fxtf-drafts/pull/314 [motion-1] 

  1 pull requests merged:
  - [motion] reverse does not appear in computed value
    https://github.com/w3c/fxtf-drafts/pull/314 [motion-1] 


Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/svgwg
* https://github.com/w3c/svg-aam
* https://github.com/w3c/fxtf-drafts
* https://github.com/w3c/graphics-aam
* https://github.com/w3c/graphics-aria