- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 23 Apr 2019 17:00:12 +0000
- To: www-svg@w3.org
- Message-Id: <E1hIymC-0007dc-1w@uranus.w3.org>
Issues ------ * w3c/svgwg (+6/-1/💬42) 6 issues created: - [svg-native] Keep in mind that some properties are not style attributes (by BigBadaboom) https://github.com/w3c/svgwg/issues/679 - [svg-native] How should currentColor be handled? (by litherum) https://github.com/w3c/svgwg/issues/678 - [svg-native] Support for font variations? (by litherum) https://github.com/w3c/svgwg/issues/677 - [svg2] "edit:excludefromidl" inconsistently applied during build (by tidoust) https://github.com/w3c/svgwg/issues/676 - [svg-native] Limited support for filters? (by litherum) https://github.com/w3c/svgwg/issues/675 - [svg-native] Should we provide a validator? (by litherum) https://github.com/w3c/svgwg/issues/674 13 issues received 42 new comments: - #670 [svg-native] support xlink:href on gradients (8 by svgeesus, dirkschulze, litherum, jarek-foksa) https://github.com/w3c/svgwg/issues/670 [SVG Native] - #672 [svg-native] Support for XML entities/CDATA required? (7 by dirkschulze, litherum, svgeesus, grorg, AmeliaBR) https://github.com/w3c/svgwg/issues/672 [SVG Native] - #664 [svg-native] What should the file extension be? (7 by svgeesus, dirkschulze, BigBadaboom, jarek-foksa) https://github.com/w3c/svgwg/issues/664 [Agenda+] [SVG Native] - #658 [svg-native] Consider supporting some subset of CSS (4 by dirkschulze, BigBadaboom, svgeesus) https://github.com/w3c/svgwg/issues/658 [SVG Native] - #674 [svg-native] Should we provide a validator? (3 by litherum, svgeesus) https://github.com/w3c/svgwg/issues/674 [SVG Native] - #669 [svg-native] Should declarations be required to be before all their uses? (3 by dirkschulze, BigBadaboom, litherum) https://github.com/w3c/svgwg/issues/669 [SVG Native] - #671 [svg-native] inner svg, symbol or use elements supported? (3 by dirkschulze, litherum, svgeesus) https://github.com/w3c/svgwg/issues/671 [SVG Native] - #665 [svg-native] What should a browser do when it encounters one of these files (2 by dirkschulze, svgeesus) https://github.com/w3c/svgwg/issues/665 [SVG Native] - #675 [svg-native] Limited support for filters? (1 by dirkschulze) https://github.com/w3c/svgwg/issues/675 - #678 [svg-native] How should currentColor be handled? (1 by dirkschulze) https://github.com/w3c/svgwg/issues/678 [SVG Native] - #657 Native profile of SVG (1 by litherum) https://github.com/w3c/svgwg/issues/657 [SVG Native] - #659 [svg-native] Consider adding masking support (1 by svgeesus) https://github.com/w3c/svgwg/issues/659 [SVG Native] - #662 [svg-native] Spec uses "deleted", "removed" and "forbidden" interchangeably (1 by svgeesus) https://github.com/w3c/svgwg/issues/662 [SVG Native] 1 issues closed: - Native profile of SVG https://github.com/w3c/svgwg/issues/657 [SVG Native] * w3c/fxtf-drafts (+0/-0/💬3) 1 issues received 3 new comments: - #256 [filter-effects-2] Add a shorthand color-channel adjustment function similar to feComponentTransfer (3 by karip, BigBadaboom) https://github.com/w3c/fxtf-drafts/issues/256 [filter-effects-2] 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, 23 April 2019 17:00:16 UTC