Weekly github digest (svgwg, fxtf-drafts)

Issues
------
* w3c/svgwg (+1/-1/💬2)
  1 issues created:
  - `text-anchor` not well specified for negative character advance (by AmeliaBR)
    https://github.com/w3c/svgwg/issues/317

  2 issues received 2 new comments:
  - #258 Allow nesting filters instead of using 'in', 'in2' and 'result' attributes (1 by SebastianZ)
    https://github.com/w3c/svgwg/issues/258
  - #317 `text-anchor` not well specified for negative character advance (1 by fsoder)
    https://github.com/w3c/svgwg/issues/317

  1 issues closed:
  - Allow nesting filters instead of using 'in', 'in2' and 'result' attributes https://github.com/w3c/svgwg/issues/258

* w3c/fxtf-drafts (+8/-7/💬30)
  8 issues created:
  - [geometry] "interface DOMRect" should have alias for ClientRect (by zcorpan)
    https://github.com/w3c/fxtf-drafts/issues/163
  - [geometry] Structured serialization should branch on is 2D (by zcorpan)
    https://github.com/w3c/fxtf-drafts/issues/161
  - Allow nesting filters instead of using 'in', 'in2' and 'result' attributes (by SebastianZ)
    https://github.com/w3c/fxtf-drafts/issues/160
  - [css-masking] Percentage for clip-path should be n/a or clarification is needed (by lahmatiy)
    https://github.com/w3c/fxtf-drafts/issues/155
  - [geometry] 0/-0 equality in "validate and fixup", isIdentity, is2D (by zcorpan)
    https://github.com/w3c/fxtf-drafts/issues/152
  - [geometry] "Rectangles have the following properties:" (by zcorpan)
    https://github.com/w3c/fxtf-drafts/issues/150
  - [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax (by fserb)
    https://github.com/w3c/fxtf-drafts/issues/149
  - [geometry] DOMMatrix stringifier in workers (by zcorpan)
    https://github.com/w3c/fxtf-drafts/issues/145

  9 issues received 30 new comments:
  - #149 [geometry] DOMMatrixReadOnly string init depends on backwards compatibility syntax (10 by zcorpan, AmeliaBR, fserb)
    https://github.com/w3c/fxtf-drafts/issues/149
  - #145 [geometry] DOMMatrix stringifier in workers (6 by zcorpan, foolip, chrishtr)
    https://github.com/w3c/fxtf-drafts/issues/145
  - #120 [geometry] DOMMatrix stringifier behavior doesn't seem to match implementations (5 by zcorpan, css-meeting-bot, AmeliaBR)
    https://github.com/w3c/fxtf-drafts/issues/120
  - #152 [geometry] 0/-0 equality in "validate and fixup", isIdentity, is2D (4 by zcorpan, domenic)
    https://github.com/w3c/fxtf-drafts/issues/152
  - #64 [motion] none value considerations (1 by ewilligers)
    https://github.com/w3c/fxtf-drafts/issues/64
  - #161 [geometry] Structured serialization should branch on is 2D (1 by zcorpan)
    https://github.com/w3c/fxtf-drafts/issues/161
  - #163 [geometry] "interface DOMRect" should have alias for ClientRect (1 by zcorpan)
    https://github.com/w3c/fxtf-drafts/issues/163
  - #117 [paint] "outside stroke" and "group outline" (1 by tobireif)
    https://github.com/w3c/fxtf-drafts/issues/117
  - #150 [geometry] "Rectangles have the following properties:" (1 by AmeliaBR)
    https://github.com/w3c/fxtf-drafts/issues/150

  7 issues closed:
  - [geometry] DOMMatrix stringifier behavior doesn't seem to match implementations https://github.com/w3c/fxtf-drafts/issues/120
  - [motion] defining "computed distance" (aka "used distance") https://github.com/w3c/fxtf-drafts/issues/74
  - [geometry] Update for structured cloning changes in HTML https://github.com/w3c/fxtf-drafts/issues/121
  - [geometry] DOMMatrix stringifier in workers https://github.com/w3c/fxtf-drafts/issues/145
  - [motion] Should omitted <size> just extend to the containing block edge? https://github.com/w3c/fxtf-drafts/issues/73
  - [geometry] " The IDL in this specification is currently in ..." https://github.com/w3c/fxtf-drafts/issues/143
  - [motion] offset-rotation should only do path-relative rotation https://github.com/w3c/fxtf-drafts/issues/69



Pull requests
-------------
* w3c/fxtf-drafts (+11/-9/💬10)
  11 pull requests submitted:
  - [geometry] Do not structured serialize -0 for m13 of a 2d matrix (by zcorpan)
    https://github.com/w3c/fxtf-drafts/pull/162
  - [geometry] Treat 0 and -0 as equal throughout (by zcorpan)
    https://github.com/w3c/fxtf-drafts/pull/159
  - [motion] Link to Motion Path's size definition (by ewilligers)
    https://github.com/w3c/fxtf-drafts/pull/158
  - [motion] computed distance now supports calc (by ewilligers)
    https://github.com/w3c/fxtf-drafts/pull/157
  - [motion] Define 'sides' value for ray size. (by ewilligers)
    https://github.com/w3c/fxtf-drafts/pull/156
  - [geometry] Add Privacy and Security Considerations (by zcorpan)
    https://github.com/w3c/fxtf-drafts/pull/154
  - [geometry] Parse as CSS 'transform' instead of SVG transform="" (by zcorpan)
    https://github.com/w3c/fxtf-drafts/pull/153
  - [geometry] Limit DOMMatrix's special stringifier to Window (by zcorpan)
    https://github.com/w3c/fxtf-drafts/pull/151
  - [geometry] Tighten up DOMMatrix's stringifier; throw for NaN/Infinity (by zcorpan)
    https://github.com/w3c/fxtf-drafts/pull/148
  - [geometry] Define serialize/deserialize steps (by zcorpan)
    https://github.com/w3c/fxtf-drafts/pull/147
  - [geometry] Remove inline issue about experimental API shape (by zcorpan)
    https://github.com/w3c/fxtf-drafts/pull/146

  8 pull requests received 10 new comments:
  - #147 [geometry] Define serialize/deserialize steps (2 by zcorpan)
    https://github.com/w3c/fxtf-drafts/pull/147
  - #148 [geometry] Tighten up DOMMatrix's stringifier; throw for NaN/Infinity (2 by zcorpan)
    https://github.com/w3c/fxtf-drafts/pull/148
  - #140 offset-rotate syntax is resolved (1 by jihyerish)
    https://github.com/w3c/fxtf-drafts/pull/140
  - #146 [geometry] Remove inline issue about experimental API shape (1 by zcorpan)
    https://github.com/w3c/fxtf-drafts/pull/146
  - #151 [geometry] Limit DOMMatrix's special stringifier to Window (1 by zcorpan)
    https://github.com/w3c/fxtf-drafts/pull/151
  - #153 [geometry] Parse as CSS 'transform' instead of SVG transform="" (1 by zcorpan)
    https://github.com/w3c/fxtf-drafts/pull/153
  - #156 [motion] Define 'sides' value for ray size. (1 by jihyerish)
    https://github.com/w3c/fxtf-drafts/pull/156
  - #159 [geometry] Treat 0 and -0 as equal throughout (1 by zcorpan)
    https://github.com/w3c/fxtf-drafts/pull/159

  9 pull requests merged:
  - [geometry] Tighten up DOMMatrix's stringifier; throw for NaN/Infinity
    https://github.com/w3c/fxtf-drafts/pull/148
  - [motion] Link to Motion Path's size definition
    https://github.com/w3c/fxtf-drafts/pull/158
  - [motion] computed distance now supports calc
    https://github.com/w3c/fxtf-drafts/pull/157
  - [geometry] Define serialize/deserialize steps
    https://github.com/w3c/fxtf-drafts/pull/147
  - [geometry] Limit DOMMatrix's special stringifier to Window
    https://github.com/w3c/fxtf-drafts/pull/151
  - [motion] Define 'sides' value for ray size.
    https://github.com/w3c/fxtf-drafts/pull/156
  - [geometry] Add Privacy and Security Considerations
    https://github.com/w3c/fxtf-drafts/pull/154
  - [geometry] Remove inline issue about experimental API shape
    https://github.com/w3c/fxtf-drafts/pull/146
  - offset-rotate syntax is resolved
    https://github.com/w3c/fxtf-drafts/pull/140


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