Weekly github digest (svgwg, fxtf-drafts)

Issues
------
* w3c/svgwg (+1/-0/💬3)
  1 issues created:
  - SVGTransform's setMatrix method should take a DOMMatrixInit (by zcorpan)
    https://github.com/w3c/svgwg/issues/326

  2 issues received 3 new comments:
  - #325 grammar for "closepath can substitute for final coordinate" is broken (2 by nikosandronikos)
    https://github.com/w3c/svgwg/issues/325
  - #326 SVGTransform's setMatrix method should take a DOMMatrixInit (1 by zcorpan)
    https://github.com/w3c/svgwg/issues/326

* w3c/fxtf-drafts (+4/-3/💬13)
  4 issues created:
  - [css-masking-1] `clip` applies-to section should mention <marker>, not <mask> (by AmeliaBR)
    https://github.com/w3c/fxtf-drafts/issues/197
  - [geometry] Method to make a DOMPoint homogeneous (by zcorpan)
    https://github.com/w3c/fxtf-drafts/issues/196
  - [geometry] WebGL API considerations (by trusktr)
    https://github.com/w3c/fxtf-drafts/issues/195
  - [geometry] DOMMatrix/DOMMatrix could use more methods and helpers. (by trusktr)
    https://github.com/w3c/fxtf-drafts/issues/194

  10 issues received 13 new comments:
  - #194 [geometry] DOMMatrix/DOMMatrix could use more methods and helpers. (2 by trusktr, zcorpan)
    https://github.com/w3c/fxtf-drafts/issues/194
  - #137 Luminance masking is slower than alpha masking (2 by jrmuizel, thebabydino)
    https://github.com/w3c/fxtf-drafts/issues/137
  - #149 [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax (2 by zcorpan, trusktr)
    https://github.com/w3c/fxtf-drafts/issues/149
  - #195 [geometry] WebGL API considerations (1 by zcorpan)
    https://github.com/w3c/fxtf-drafts/issues/195
  - #196 [geometry] Method to make a DOMPoint homogeneous (1 by fuchsia)
    https://github.com/w3c/fxtf-drafts/issues/196
  - #139 [filter-effects] List feMergeNode in the TOC (1 by SebastianZ)
    https://github.com/w3c/fxtf-drafts/issues/139
  - #108 [motion] Define offset-rotate at sharp path segment boundaries (1 by jihyerish)
    https://github.com/w3c/fxtf-drafts/issues/108
  - #45 [css-motion] description of offset-position should be clearer (1 by ewilligers)
    https://github.com/w3c/fxtf-drafts/issues/45
  - #109 [motion] Offset-rotate and zero length paths (1 by jihyerish)
    https://github.com/w3c/fxtf-drafts/issues/109
  - #57 [motion-1] description of interactions should be a little bit more formal (1 by jihyerish)
    https://github.com/w3c/fxtf-drafts/issues/57

  3 issues closed:
  - [motion] Define offset-rotate at sharp path segment boundaries https://github.com/w3c/fxtf-drafts/issues/108
  - [motion] Offset-rotate and zero length paths https://github.com/w3c/fxtf-drafts/issues/109
  - [motion-1] description of interactions should be a little bit more formal https://github.com/w3c/fxtf-drafts/issues/57



Pull requests
-------------
* w3c/fxtf-drafts (+0/-0/💬1)
  1 pull requests received 1 new comments:
  - #187 [geometry] Define better how to transform a point with a matrix (1 by zcorpan)
    https://github.com/w3c/fxtf-drafts/pull/187


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