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

Issues
------
* w3c/svgwg (+7/-1/💬32)
  7 issues created:
  - Do we really need not to reflect additional enum values in SVG 2 (by longsonr)
    https://github.com/w3c/svgwg/issues/424 
  - What should happen if you try to set an out of range value on an enum in the DOM (by longsonr)
    https://github.com/w3c/svgwg/issues/423 
  - Bounding box algorithm is not precise (by dirkschulze)
    https://github.com/w3c/svgwg/issues/422 [Co-ordinates chapter] 
  - context-value UA rules for OpenType are giving unexpected rendering / compat problems (by emilio)
    https://github.com/w3c/svgwg/issues/421 
  - Start using URL (instead of URI reference) (by annevk)
    https://github.com/w3c/svgwg/issues/420 
  - Use <dfn> for definitions (by fantasai)
    https://github.com/w3c/svgwg/issues/417 
  - Clarify relation of isPointInFill and pointer-events (by dirkschulze)
    https://github.com/w3c/svgwg/issues/416 

  8 issues received 32 new comments:
  - #417 Use <dfn> for definitions (9 by dirkschulze, tabatkins, dstorey, plinss)
    https://github.com/w3c/svgwg/issues/417 
  - #422 Bounding box algorithm is not precise (6 by dirkschulze, BigBadaboom)
    https://github.com/w3c/svgwg/issues/422 [Co-ordinates chapter] 
  - #416 Clarify relation of isPointInFill and pointer-events (4 by dirkschulze, AmeliaBR)
    https://github.com/w3c/svgwg/issues/416 [Agenda+] [Basic Data Types and Interfaces chapter] 
  - #424 Do we really need not to reflect additional enum values in SVG 2 (4 by longsonr, dirkschulze)
    https://github.com/w3c/svgwg/issues/424 
  - #419 Rename SVGBoundingBoxOptions to SVGBoundingBoxOptionsInit (3 by dirkschulze, dstorey)
    https://github.com/w3c/svgwg/issues/419 [Basic Data Types and Interfaces chapter] 
  - #421 context-value UA rules for OpenType are giving unexpected rendering / compat problems (3 by upsuper, AmeliaBR)
    https://github.com/w3c/svgwg/issues/421 
  - #335 SVG2 path data coordinates are currently spec'd as integers. (2 by fuchsia, AmeliaBR)
    https://github.com/w3c/svgwg/issues/335 [Paths chapter] [SVG Core] 
  - #420 Start using URL (instead of URI reference) (1 by dirkschulze)
    https://github.com/w3c/svgwg/issues/420 

  1 issues closed:
  - Move dataset & other shared IDL attributes from SVGElement to HTMLOrSVGElement https://github.com/w3c/svgwg/issues/60 [Basic Data Types and Interfaces chapter] [Needs editing] [SVG Core] 

* w3c/fxtf-drafts (+2/-1/💬14)
  2 issues created:
  - Investigate removing [LegacyArrayClass] from DOMRectList (by annevk)
    https://github.com/w3c/fxtf-drafts/issues/280 
  - [css-masking-1] stroke-bounding-box and non-scaling-stroke (by dirkschulze)
    https://github.com/w3c/fxtf-drafts/issues/279 [Agenda+] [Needs SVGWG Input/Decision] [css-masking-1] 

  5 issues received 14 new comments:
  - #53 [filters] Backdrop filters should not use BackgroundImage (5 by dirkschulze, mstange, AmeliaBR)
    https://github.com/w3c/fxtf-drafts/issues/53 [filter-effects-2] 
  - #280 Investigate removing [LegacyArrayClass] from DOMRectList (4 by dirkschulze, csnardi)
    https://github.com/w3c/fxtf-drafts/issues/280 [geometry-1] 
  - #124 [geometry] Why does DOMQuad have readonly mutable points? (3 by dirkschulze, tabatkins, bzbarsky)
    https://github.com/w3c/fxtf-drafts/issues/124 [Needs CSSWG Input/Decision] [geometry-1] 
  - #195 [geometry] WebGL API considerations (1 by dirkschulze)
    https://github.com/w3c/fxtf-drafts/issues/195 [Commenter Response Pending] [geometry-1] 
  - #222 [geometry] DOMRect: use of unrestricted doubles - min(x, NaN) (1 by bzbarsky)
    https://github.com/w3c/fxtf-drafts/issues/222 [geometry-1] 

  1 issues closed:
  - [geometry] JSON serialization of a DOMRectList https://github.com/w3c/fxtf-drafts/issues/199 [Closed Rejected as Wontfix] [Commenter Satisfied] [geometry-1] 



Pull requests
-------------
* w3c/svgwg (+2/-2/💬16)
  2 pull requests submitted:
  - Keep the linting minions happy (by dstorey)
    https://github.com/w3c/svgwg/pull/418 
  - Add HTMLOrSVGElement mixn (by dstorey)
    https://github.com/w3c/svgwg/pull/415 

  4 pull requests received 16 new comments:
  - #415 Add HTMLOrSVGElement mixn (11 by tobie, dirkschulze, dstorey, AmeliaBR)
    https://github.com/w3c/svgwg/pull/415 
  - #398 Remove support for segment-completing close path (2 by dirkschulze)
    https://github.com/w3c/svgwg/pull/398 
  - #413 Add DocumentAndElementEventHandlers (2 by dstorey)
    https://github.com/w3c/svgwg/pull/413 
  - #346 Fixed path grammar  (1 by AmeliaBR)
    https://github.com/w3c/svgwg/pull/346 

  2 pull requests merged:
  - Keep the linting minions happy
    https://github.com/w3c/svgwg/pull/418 
  - Add HTMLOrSVGElement mixn
    https://github.com/w3c/svgwg/pull/415 


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