- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 09 May 2017 17:00:04 +0000
- To: www-svg@w3.org
- Message-Id: <E1d88UW-0001HV-Jy@uranus.w3.org>
Issues
------
* w3c/svgwg (+3/-1/💬6)
3 issues created:
- Add a presentation attribute for `paint-order` (by AmeliaBR)
https://github.com/w3c/svgwg/issues/316
- SVGAElement webidl issues (by longsonr)
https://github.com/w3c/svgwg/issues/315
- Should support nomodule attribute on script elements (by bzbarsky)
https://github.com/w3c/svgwg/issues/314
3 issues received 6 new comments:
- #315 SVGAElement all attributes except href should be as HTML i.e. not SVGAnimatedString (4 by longsonr, AmeliaBR)
https://github.com/w3c/svgwg/issues/315
- #312 SVGAElement implements two conflicting interfaces (1 by longsonr)
https://github.com/w3c/svgwg/issues/312
- #314 Should support nomodule attribute on script elements (1 by AmeliaBR)
https://github.com/w3c/svgwg/issues/314
1 issues closed:
- SVGAElement webidl issues https://github.com/w3c/svgwg/issues/315
* w3c/fxtf-drafts (+2/-3/💬6)
2 issues created:
- [geometry] Clarify parsing of new DOMMatrix(string) (by zcorpan)
https://github.com/w3c/fxtf-drafts/issues/144
- [geometry] " The IDL in this specification is currently in ..." (by zcorpan)
https://github.com/w3c/fxtf-drafts/issues/143
3 issues received 6 new comments:
- #120 [geometry] DOMMatrix stringifier behavior doesn't seem to match implementations (4 by zcorpan, gogag1)
https://github.com/w3c/fxtf-drafts/issues/120
- #122 [geometry] DOMMatrix should not depend on the CSS parser (1 by zcorpan)
https://github.com/w3c/fxtf-drafts/issues/122
- #55 [geometry] Usage of 'none' in DOMMatrix transform lists (1 by zcorpan)
https://github.com/w3c/fxtf-drafts/issues/55
3 issues closed:
- [geometry] DOMMatrix should not depend on the CSS parser https://github.com/w3c/fxtf-drafts/issues/122
- [geometry] Usage of 'none' in DOMMatrix transform lists https://github.com/w3c/fxtf-drafts/issues/55
- [geometry] Avoid overloading constructor for DOMMatrix https://github.com/w3c/fxtf-drafts/issues/135
Pull requests
-------------
* w3c/fxtf-drafts (+3/-3/💬4)
3 pull requests submitted:
- [geometry] Annotate DOMMatrix's mutable methods with [NewObject] (by zcorpan)
https://github.com/w3c/fxtf-drafts/pull/142
- [geometry] Do not expose CSS parser in workers for DOMMatrix (by zcorpan)
https://github.com/w3c/fxtf-drafts/pull/141
- offset-rotate syntax is resolved (by ewilligers)
https://github.com/w3c/fxtf-drafts/pull/140
2 pull requests received 4 new comments:
- #136 [geometry] Use union instead of overload for DOMMatrix/DOMMatrixReadO… (3 by zcorpan, annevk)
https://github.com/w3c/fxtf-drafts/pull/136
- #142 [geometry] Annotate DOMMatrix's mutable methods with [NewObject] (1 by zcorpan)
https://github.com/w3c/fxtf-drafts/pull/142
3 pull requests merged:
- [geometry] Annotate DOMMatrix's immutable methods with [NewObject]
https://github.com/w3c/fxtf-drafts/pull/142
- [geometry] Do not expose CSS parser in workers for DOMMatrix
https://github.com/w3c/fxtf-drafts/pull/141
- [geometry] Use union instead of overload for DOMMatrix/DOMMatrixReadO…
https://github.com/w3c/fxtf-drafts/pull/136
Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/svgwg
* https://github.com/w3c/fxtf-drafts
Received on Tuesday, 9 May 2017 17:00:11 UTC