- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 13 Dec 2022 17:00:38 +0000
- To: www-svg@w3.org
- Message-Id: <E1p58dy-002p3n-AW@uranus.w3.org>
Issues
------
* w3c/svg-aam (+1/-0/💬2)
1 issues created:
- Browsers off spec? SVG maps to "group" but the spec suggests it should map to "graphics-document" (by brennanyoung)
https://github.com/w3c/svg-aam/issues/22
2 issues received 2 new comments:
- #18 Should the mappings of a nested 'svg' be different from that of a root 'svg'? (1 by brennanyoung)
https://github.com/w3c/svg-aam/issues/18
- #17 When is the "symbol" element mappable? (1 by brennanyoung)
https://github.com/w3c/svg-aam/issues/17
* w3c/fxtf-drafts (+1/-0/💬0)
1 issues created:
- [filter-effects-1] Broken references in Filter Effects Module Level 1 (by dontcallmedom-bot)
https://github.com/w3c/fxtf-drafts/issues/482
Pull requests
-------------
* w3c/svgwg (+2/-0/💬8)
2 pull requests submitted:
- Svg next (by hackermondal)
https://github.com/w3c/svgwg/pull/902
- Remove support for data: URL in SVGUseElement (by shhnjk)
https://github.com/w3c/svgwg/pull/901
2 pull requests received 8 new comments:
- #902 Svg next (3 by hackermondal)
https://github.com/w3c/svgwg/pull/902
- #901 Remove support for data: URL in SVGUseElement (5 by caribouW3, mozfreddyb, shhnjk, w3cbot)
https://github.com/w3c/svgwg/pull/901
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
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 13 December 2022 17:00:40 UTC