W3C home > Mailing lists > Public > www-svg@w3.org > December 2016

Weekly digest of github activity (svgwg, fxtf-drafts)

From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
Date: Tue, 06 Dec 2016 17:00:03 +0000
To: www-svg@w3.org
Message-Id: <E1cEJ63-00054S-98@uranus.w3.org>


Issues
------
* w3c/svgwg (+1/-0/💬0)
  1 issues created:
  - Add advice on how to handle className conflict in DOM (by 
BigBadaboom)
    https://github.com/w3c/svgwg/issues/298

* w3c/fxtf-drafts (+1/-2/💬15)
  1 issues created:
  - [css-masking] How does masking apply to table parts? (by dbaron)
    https://github.com/w3c/fxtf-drafts/issues/94

  2 issues closed:
  - [motion][naming] offset-rotation vs rotate 
https://github.com/w3c/fxtf-drafts/issues/70
  - [css-masking-1] [filters] Remove "* implements SVGUnitTypes" 
https://github.com/w3c/fxtf-drafts/issues/90

  10 issues received 15 new comments:
  - #70 [motion][naming] offset-rotation vs rotate (4 by ewilligers, 
yisibl, jihyerish)
    https://github.com/w3c/fxtf-drafts/issues/70
  - #65 [motion] Should failed references be treated as `none` or as a
 `0deg` zero-length path? (2 by ewilligers, jihyerish)
    https://github.com/w3c/fxtf-drafts/issues/65
  - #69 [motion] offset-rotation should only do path-relative rotation
 (2 by shans)
    https://github.com/w3c/fxtf-drafts/issues/69
  - #64 [motion] none value considerations (1 by ewilligers)
    https://github.com/w3c/fxtf-drafts/issues/64
  - #79 [motion] Use 'position: relative' instead of 'opacity: 0' for 
stacking context descriptions (1 by ewilligers)
    https://github.com/w3c/fxtf-drafts/issues/79
  - #77 [motion] Interaction with positioning (1 by jihyerish)
    https://github.com/w3c/fxtf-drafts/issues/77
  - #45 [css-motion] description of offset-position should be clearer 
(1 by jihyerish)
    https://github.com/w3c/fxtf-drafts/issues/45
  - #51 [css-motion] offset-* property names collide with logical 
properties (1 by yisibl)
    https://github.com/w3c/fxtf-drafts/issues/51
  - #90 [css-masking-1] [filters] Remove "* implements SVGUnitTypes" 
(1 by foolip)
    https://github.com/w3c/fxtf-drafts/issues/90
  - #59 [motion-1] examples could be clearer (1 by jihyerish)
    https://github.com/w3c/fxtf-drafts/issues/59


Pull requests
-------------
* w3c/fxtf-drafts (+2/-2/💬1)
  2 pull requests submitted:
  - [motion] offset-rotation becomes offset-rotate (by ewilligers)
    https://github.com/w3c/fxtf-drafts/pull/96
  - SVGClipPathElement and SVGMaskElement no longer implement 
SVGUnitTypes. (by nikosandronikos)
    https://github.com/w3c/fxtf-drafts/pull/95

  2 pull requests merged:
  - [motion] offset-rotation becomes offset-rotate
    https://github.com/w3c/fxtf-drafts/pull/96
  - SVGFilterElement must not implement SVGUnitTypes.
    https://github.com/w3c/fxtf-drafts/pull/93

  1 pull requests received 1 new comments:
  - #96 [motion] offset-rotation becomes offset-rotate (1 by 
jihyerish)
    https://github.com/w3c/fxtf-drafts/pull/96


Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/svgwg
* https://github.com/w3c/fxtf-drafts
Received on Tuesday, 6 December 2016 17:00:10 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:46 UTC