Weekly github digest (svgwg, svg-aam, fxtf-drafts, graphics-aam, graphics-aria) from W3C Webmaster via GitHub API on 2018-11-13 (www-svg@w3.org from November 2018)

From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
Date: Tue, 13 Nov 2018 17:00:13 +0000
To: www-svg@w3.org
Message-Id: <E1gMc2v-0001pF-CG@uranus.w3.org>
Issues
------
* w3c/svgwg (+8/-6/💬66)
  8 issues created:
  - Defer text content area (by dirkschulze)
    https://github.com/w3c/svgwg/issues/589 [Text chapter] 
  - 'stop-color' property resolving with 'inherit' value (by RazrFalcon)
    https://github.com/w3c/svgwg/issues/588 
  - The filter region clipping (by RazrFalcon)
    https://github.com/w3c/svgwg/issues/587 
  - vector-effect host coordinate space is not "screen" (by dirkschulze)
    https://github.com/w3c/svgwg/issues/582 [Agenda+] [Co-ordinates chapter] [Needs editing] 
  - pointer-events: remove requirement to scan pixels on images (by dirkschulze)
    https://github.com/w3c/svgwg/issues/581 [Agenda+] [Scripting chapter] 
  - should textPath elements parented to tspans or other textPaths render? (by heycam)
    https://github.com/w3c/svgwg/issues/580 
  - how should display:contents affect SVG conditional processing attributes? (by heycam)
    https://github.com/w3c/svgwg/issues/579 
  - Drawing vector-effects mentions SVG 1.2T terms (by dirkschulze)
    https://github.com/w3c/svgwg/issues/578 [Needs editing] [Painting chapter] 

  18 issues received 66 new comments:
  - #456 isPointInFill/isPointInStroke and display: none and other specifics (9 by longsonr, dirkschulze, fsoder, css-meeting-bot)
    https://github.com/w3c/svgwg/issues/456 [Basic Data Types and Interfaces chapter] 
  - #306 Since vector-effect options other than non-scaling-stroke already have multiple implementations, is the "at risk" flag valid? (8 by longsonr, dirkschulze, Tavmjong, satakagi)
    https://github.com/w3c/svgwg/issues/306 [Entire spec] [Has tests] [Needs editing] 
  - #587 The filter region clipping (7 by dirkschulze, RazrFalcon, fsoder)
    https://github.com/w3c/svgwg/issues/587 
  - #588 'stop-color' property resolving with 'inherit' value (7 by dirkschulze, RazrFalcon, fsoder, Tavmjong)
    https://github.com/w3c/svgwg/issues/588 
  - #322 Remove un-implemented `pointer-events` "painted" rules for images (5 by dirkschulze, fsoder, css-meeting-bot)
    https://github.com/w3c/svgwg/issues/322 [SVG Core] [Scripting chapter] 
  - #582 vector-effect host coordinate space is not "screen" (5 by dirkschulze, css-meeting-bot)
    https://github.com/w3c/svgwg/issues/582 [Co-ordinates chapter] [Needs editing] 
  - #537 Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes. (5 by r12a, dirkschulze, litherum, Tavmjong)
    https://github.com/w3c/svgwg/issues/537 [Needs editing] [Needs tests] [Text chapter] [i18n-tracking] 
  - #573 pointer-events bounding-box (4 by longsonr, ewilligers, dirkschulze)
    https://github.com/w3c/svgwg/issues/573 [Interactivity chapter] [Needs data] 
  - #580 should textPath elements parented to tspans or other textPaths render? (3 by tabatkins, heycam)
    https://github.com/w3c/svgwg/issues/580 [Needs editing] [Text chapter] 
  - #581 pointer-events: remove requirement to scan pixels on images (3 by dirkschulze, BigBadaboom)
    https://github.com/w3c/svgwg/issues/581 [Agenda+] [Scripting chapter] 
  - #323 How does vector-effect=non-scaling-stroke interact with the stroke-dash* properties (2 by dirkschulze, css-meeting-bot)
    https://github.com/w3c/svgwg/issues/323 [Painting chapter] [SVG Core] 
  - #553 Defer z-index due to lack of implementations (2 by dirkschulze)
    https://github.com/w3c/svgwg/issues/553 [Rendering Model chapter] [SVG Core] 
  - #68 Develop a new standard for describing "layers" in SVG authoring tools (1 by dirkschulze)
    https://github.com/w3c/svgwg/issues/68 [Proposal] 
  - #545 stroke-miterlimit: invalid value behavior? (1 by dirkschulze)
    https://github.com/w3c/svgwg/issues/545 [CSS Consistency] [Need to file UA bug] [Needs tests] [Painting chapter] [SVG Core] 
  - #326 SVGTransform's setMatrix method should take a DOMMatrix2DInit (1 by css-meeting-bot)
    https://github.com/w3c/svgwg/issues/326 [Needs tests] 
  - #589 Defer text content area (1 by dirkschulze)
    https://github.com/w3c/svgwg/issues/589 [Text chapter] 
  - #579 how should display:contents affect SVG conditional processing attributes? (1 by dirkschulze)
    https://github.com/w3c/svgwg/issues/579 [CSS Consistency] 
  - #511 <foreignObject> and <svg:use> (1 by css-meeting-bot)
    https://github.com/w3c/svgwg/issues/511 [Embedded Content chapter] 

  6 issues closed:
  - Defer z-index due to lack of implementations https://github.com/w3c/svgwg/issues/553 [Rendering Model chapter] [SVG Core] 
  - 'stop-color' property resolving with 'inherit' value https://github.com/w3c/svgwg/issues/588 
  - The filter region clipping https://github.com/w3c/svgwg/issues/587 
  - stroke-miterlimit: invalid value behavior? https://github.com/w3c/svgwg/issues/545 [CSS Consistency] [Need to file UA bug] [Needs tests] [Painting chapter] [SVG Core] 
  - pointer-events: remove requirement to scan pixels on images https://github.com/w3c/svgwg/issues/581 [Agenda+] [Scripting chapter] 
  - pointer-events auto https://github.com/w3c/svgwg/issues/574 [Interactivity chapter] 

* w3c/fxtf-drafts (+4/-7/💬32)
  4 issues created:
  - [filter-effect] The filter region clipping (by dirkschulze)
    https://github.com/w3c/fxtf-drafts/issues/321 [filter-effects-1] 
  - [geometry-1] scaleY for scale() not defined if missing (by dirkschulze)
    https://github.com/w3c/fxtf-drafts/issues/319 [Needs Edits] [geometry-1] 
  - [geometry-1] Default initialize DOMMatrix2DInit (by dirkschulze)
    https://github.com/w3c/fxtf-drafts/issues/316 
  - [css-transforms-2] Serialize the individual transform if the animation is at 0% and 100% (by BorisChiou)
    https://github.com/w3c/fxtf-drafts/issues/315 

  11 issues received 32 new comments:
  - #53 [filter-effects-2] Backdrop filters should not use BackgroundImage (9 by smfr, Benimation, mfreed7, mstange, AmeliaBR)
    https://github.com/w3c/fxtf-drafts/issues/53 [Agenda+] [filter-effects-2] 
  - #214 [geometry] Restore DOMMatrixReadOnly.scaleNonUniform() for backward compatibility with SVGMatrix (6 by zcorpan, dirkschulze, foolip)
    https://github.com/w3c/fxtf-drafts/issues/214 [Needs WPT test] [geometry-1] 
  - #313 [css-transforms-2] How to serialize `scale` if we only use one number? (6 by tabatkins, birtles, BorisChiou)
    https://github.com/w3c/fxtf-drafts/issues/313 
  - #315 [css-transforms-2] Serialize the individual transform if the animation is at 0% and 100% (3 by dirkschulze, BorisChiou)
    https://github.com/w3c/fxtf-drafts/issues/315 
  - #269 [geometry] Specify stringifier for DOMRectList (2 by dirkschulze)
    https://github.com/w3c/fxtf-drafts/issues/269 [Closed Rejected as Invalid] [geometry-1] 
  - #316 [geometry-1] Default initialize DOMMatrix2DInit (1 by dirkschulze)
    https://github.com/w3c/fxtf-drafts/issues/316 [geometry-1] 
  - #271 [geometry] Matrix method inverse() doesn't suggest an inverse algorithm (1 by dirkschulze)
    https://github.com/w3c/fxtf-drafts/issues/271 [geometry-1] 
  - #272 [geometry] DOMRect could be clearer about the sign of contained zeroes (1 by dirkschulze)
    https://github.com/w3c/fxtf-drafts/issues/272 [geometry-1] 
  - #274 [geometry] " If x and y should both be zero, the angle is s..." (1 by dirkschulze)
    https://github.com/w3c/fxtf-drafts/issues/274 [Closed Rejected as Invalid] [geometry-1] 
  - #124 [geometry] Why does DOMQuad have readonly mutable points? (1 by dirkschulze)
    https://github.com/w3c/fxtf-drafts/issues/124 [Needs CSSWG Input/Decision] [geometry-1] 
  - #319 [geometry-1] scaleY for scale() not defined if missing (1 by zcorpan)
    https://github.com/w3c/fxtf-drafts/issues/319 [Needs Edits] [geometry-1] 

  7 issues closed:
  - [geometry] DOMRect could be clearer about the sign of contained zeroes https://github.com/w3c/fxtf-drafts/issues/272 [geometry-1] 
  - [geometry] Restore DOMMatrixReadOnly.scaleNonUniform() for backward compatibility with SVGMatrix https://github.com/w3c/fxtf-drafts/issues/214 [Needs WPT test] [geometry-1] 
  - [geometry-1] scaleY for scale() not defined if missing https://github.com/w3c/fxtf-drafts/issues/319 [Needs Edits] [geometry-1] 
  - [geometry] Specify stringifier for DOMRectList https://github.com/w3c/fxtf-drafts/issues/269 [Closed Rejected as Invalid] [geometry-1] 
  - [geometry] " If x and y should both be zero, the angle is s..." https://github.com/w3c/fxtf-drafts/issues/274 [Closed Rejected as Invalid] [geometry-1] 
  - [geometry-1] Default initialize DOMMatrix2DInit https://github.com/w3c/fxtf-drafts/issues/316 [Closed Rejected as Invalid] [geometry-1] 
  - [css-transforms-2] Serialize the individual transform if the animation is at 0% and 100% https://github.com/w3c/fxtf-drafts/issues/315 



Pull requests
-------------
* w3c/svgwg (+7/-1/💬3)
  7 pull requests submitted:
  - inline-size has initial value auto (by ewilligers)
    https://github.com/w3c/svgwg/pull/590 [Text chapter] 
  - Unify CSS properties, use new animation type attributes, allow number… (by dirkschulze)
    https://github.com/w3c/svgwg/pull/586 
  - Adapt host coordinate space def of vector-effect to implemented behav… (by dirkschulze)
    https://github.com/w3c/svgwg/pull/585 
  - Clarify pointer-events with clipping path on bounding-box and remove … (by dirkschulze)
    https://github.com/w3c/svgwg/pull/584 
  - isPointInStroke must take vector-effect property into account. #559 (by dirkschulze)
    https://github.com/w3c/svgwg/pull/583 
  - Use DOMMatrix2DInit as parameters for methods. #326 (by dirkschulze)
    https://github.com/w3c/svgwg/pull/577 
  - Remove at-risk flag from vector-effect values (by dirkschulze)
    https://github.com/w3c/svgwg/pull/576 

  3 pull requests received 3 new comments:
  - #586 Unify CSS properties, use new animation type attributes, allow number… (1 by dirkschulze)
    https://github.com/w3c/svgwg/pull/586 
  - #590 inline-size has initial value auto (1 by ewilligers)
    https://github.com/w3c/svgwg/pull/590 [Text chapter] 
  - #576 Remove at-risk flag from vector-effect values (1 by dirkschulze)
    https://github.com/w3c/svgwg/pull/576 

  1 pull requests merged:
  - [interactivity] pointer-events auto
    https://github.com/w3c/svgwg/pull/575 [Interactivity chapter] 

* w3c/fxtf-drafts (+3/-2/💬3)
  3 pull requests submitted:
  - [geometry-1] Clarify what happens on missing scaleY for scale() funct… (by dirkschulze)
    https://github.com/w3c/fxtf-drafts/pull/320 
  - [geometry-1] Re-add scaleNonUniform for compat reasons to SVGMatrix. … (by dirkschulze)
    https://github.com/w3c/fxtf-drafts/pull/318 
  - Default initialize DOMMatrix2DInit elements. #316 (by dirkschulze)
    https://github.com/w3c/fxtf-drafts/pull/317 

  2 pull requests received 3 new comments:
  - #318 [geometry-1] Re-add scaleNonUniform for compat reasons to SVGMatrix. … (2 by zcorpan, dirkschulze)
    https://github.com/w3c/fxtf-drafts/pull/318 
  - #317 [geometry-1] Default initialize DOMMatrix2DInit elements. #316 (1 by dirkschulze)
    https://github.com/w3c/fxtf-drafts/pull/317 

  2 pull requests merged:
  - [geometry-1] Re-add scaleNonUniform for compat reasons to SVGMatrix. …
    https://github.com/w3c/fxtf-drafts/pull/318 
  - [geometry-1] Clarify what happens on missing scaleY for scale() funct…
    https://github.com/w3c/fxtf-drafts/pull/320 


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
Received on Tuesday, 13 November 2018 17:00:15 UTC