Weekly github digest (svgwg, fxtf-drafts)

Issues
------
* w3c/svgwg (+1/-0/💬6)
  1 issues created:
  - getPathSegAtLength had consistent implementation behavior for invalid paths (by progers)
    https://github.com/w3c/svgwg/issues/313

  4 issues received 6 new comments:
  - #305 SVG and CSS display:contents (3 by tabatkins, dbaron, AmeliaBR)
    https://github.com/w3c/svgwg/issues/305
  - #313 getPathSegAtLength had consistent implementation behavior for invalid paths (1 by AmeliaBR)
    https://github.com/w3c/svgwg/issues/313
  - #260 Rotating text (1 by r12a)
    https://github.com/w3c/svgwg/issues/260
  - #261 inline-base direction (1 by r12a)
    https://github.com/w3c/svgwg/issues/261

* w3c/fxtf-drafts (+3/-2/💬17)
  3 issues created:
  - [fill-stroke] Add fill-blend-mode and stroke-blend-mode properties (by AmeliaBR)
    https://github.com/w3c/fxtf-drafts/issues/134
  - [geometry] Cross-references within rectangle properties (by cvrebert)
    https://github.com/w3c/fxtf-drafts/issues/133
  - [geometry] Gloss "viewport" (by cvrebert)
    https://github.com/w3c/fxtf-drafts/issues/132

  11 issues received 17 new comments:
  - #73 [motion] Should omitted <size> just extend to the containing block edge? (3 by jihyerish, css-meeting-bot)
    https://github.com/w3c/fxtf-drafts/issues/73
  - #51 [css-motion] offset-* property names collide with logical properties (3 by jonathantneal, css-meeting-bot, shans)
    https://github.com/w3c/fxtf-drafts/issues/51
  - #78 [motion] No model for interaction of `offset-position` and shapes (2 by css-meeting-bot, shans)
    https://github.com/w3c/fxtf-drafts/issues/78
  - #123 [geometry] Consider using Typed Arrays for matrices and static transform operations (2 by foolip)
    https://github.com/w3c/fxtf-drafts/issues/123
  - #66 [motion] CSS and SVG box correspondence seems overly-simplistic (1 by dbaron)
    https://github.com/w3c/fxtf-drafts/issues/66
  - #132 [geometry] Gloss "viewport" (1 by AmeliaBR)
    https://github.com/w3c/fxtf-drafts/issues/132
  - #69 [motion] offset-rotation should only do path-relative rotation (1 by css-meeting-bot)
    https://github.com/w3c/fxtf-drafts/issues/69
  - #74 [motion] defining "computed distance" (aka "used distance") (1 by shans)
    https://github.com/w3c/fxtf-drafts/issues/74
  - #130 [css-masking] make the behavior of an invalid mask  be consistent with clip-path and filter (1 by AmeliaBR)
    https://github.com/w3c/fxtf-drafts/issues/130
  - #79 [motion] Use 'position: relative' instead of 'opacity: 0' for stacking context descriptions (1 by fantasai)
    https://github.com/w3c/fxtf-drafts/issues/79
  - #122 [geometry] DOMMatrix should not depend on the CSS parser (1 by foolip)
    https://github.com/w3c/fxtf-drafts/issues/122

  2 issues closed:
  - [motion] contain should modify percentages, not path https://github.com/w3c/fxtf-drafts/issues/61
  - [motion] defining "computed distance" (aka "used distance") https://github.com/w3c/fxtf-drafts/issues/74



Pull requests
-------------
* w3c/fxtf-drafts (+0/-1/💬0)
  1 pull requests merged:
  - No rotation when path is none
    https://github.com/w3c/fxtf-drafts/pull/125


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