Weekly github digest (svgwg, fxtf-drafts)

Issues
------
* w3c/svgwg (+1/-0/💬3)
  1 issues created:
  - SVGAElement implements two conflicting interfaces (by SaschaNaz)
    https://github.com/w3c/svgwg/issues/312

  2 issues received 3 new comments:
  - #306 Since vector-effect options other than non-scaling-stroke already have multiple implementations, is the "at risk" flag valid? (2 by tabatkins, svgeesus)
    https://github.com/w3c/svgwg/issues/306
  - #312 SVGAElement implements two conflicting interfaces (1 by AmeliaBR)
    https://github.com/w3c/svgwg/issues/312

* w3c/fxtf-drafts (+2/-0/💬6)
  2 issues created:
  - [filter-effects] Clarify the colour spaces used (by debarshiray)
    https://github.com/w3c/fxtf-drafts/issues/127
  - [transforms-2] Dubious definition of perspective(0) (by nox)
    https://github.com/w3c/fxtf-drafts/issues/126

  4 issues received 6 new comments:
  - #11 filter should be defined to establish a containing block for fixed and absolutely positioned elements (2 by chrishtr, bzbarsky)
    https://github.com/w3c/fxtf-drafts/issues/11
  - #126 [transforms-2] Dubious definition of perspective(0) (2 by emilio, AmeliaBR)
    https://github.com/w3c/fxtf-drafts/issues/126
  - #122 [geometry] DOMMatrix should not depend on the CSS parser (1 by chrishtr)
    https://github.com/w3c/fxtf-drafts/issues/122
  - #123 [geometry] Consider using Typed Arrays for matrices and static transform operations (1 by chrishtr)
    https://github.com/w3c/fxtf-drafts/issues/123




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