- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 22 May 2018 17:00:06 +0000
- To: www-svg@w3.org
- Message-Id: <E1fLAdq-0006V3-0R@uranus.w3.org>
Issues
------
* w3c/svgwg (+5/-2/💬18)
5 issues created:
- stacking context / rendering order requirements are mostly not Web compatible (by heycam)
https://github.com/w3c/svgwg/issues/463
- SVG...List.removeItem not specified to reserialize to attribute (by fsoder)
https://github.com/w3c/svgwg/issues/461
- Definitions not marked as export (by dirkschulze)
https://github.com/w3c/svgwg/issues/459
- isPointInFill/isPointInStroke and display: none and other specifics (by dirkschulze)
https://github.com/w3c/svgwg/issues/456
- Clean up assets once all removals/referments from SVG2 are merged (by dstorey)
https://github.com/w3c/svgwg/issues/454 [SVG2]
7 issues received 18 new comments:
- #421 context-value UA rules for OpenType are giving unexpected rendering / compat problems (6 by svgeesus, AmeliaBR)
https://github.com/w3c/svgwg/issues/421 [SVG in OpenType] [Styling chapter]
- #462 Define "context" for SVG-in-OpenType glyphs (3 by svgeesus, Tavmjong, AmeliaBR)
https://github.com/w3c/svgwg/issues/462 [Painting chapter] [SVG Core] [SVG in OpenType] [SVG2]
- #449 Update SVG 2.0 (master) to remove "at-risk" features, preserve in svg-next (Wave 1: Hatch, Mesh, Cursor, Solid color) (2 by dstorey, boggydigital)
https://github.com/w3c/svgwg/issues/449
- #456 isPointInFill/isPointInStroke and display: none and other specifics (2 by dirkschulze, AmeliaBR)
https://github.com/w3c/svgwg/issues/456
- #459 Definitions not marked as export (2 by dstorey, plinss)
https://github.com/w3c/svgwg/issues/459
- #463 stacking context / rendering order requirements are mostly not Web compatible (2 by heycam, AmeliaBR)
https://github.com/w3c/svgwg/issues/463
- #348 Allow setting the SVG context properties when in an HTML <img> tag (1 by AmeliaBR)
https://github.com/w3c/svgwg/issues/348
2 issues closed:
- Update SVG 2.0 (master) to remove "at-risk" features, preserve in svg-next (Wave 1: Hatch, Mesh, Cursor, Solid color) https://github.com/w3c/svgwg/issues/449
- Definitions not marked as export https://github.com/w3c/svgwg/issues/459
* w3c/fxtf-drafts (+2/-1/💬10)
2 issues created:
- Current Transform Matrix (CTM) setup to not export (by dstorey)
https://github.com/w3c/fxtf-drafts/issues/289
- Link to fespecularlighting surfaceScale fails linting in SVG spec due to not exporting it in filters spec (by dstorey)
https://github.com/w3c/fxtf-drafts/issues/287
6 issues received 10 new comments:
- #289 Current Transform Matrix (CTM) setup to not export (3 by dirkschulze, dstorey)
https://github.com/w3c/fxtf-drafts/issues/289
- #245 [css-masking] Disabling masks and clipPaths when display is none (3 by dirkschulze)
https://github.com/w3c/fxtf-drafts/issues/245 [Agenda+] [Needs SVGWG Input/Decision] [css-masking-1]
- #130 [css-masking] make the behavior of an invalid mask be consistent with clip-path and filter (1 by dirkschulze)
https://github.com/w3c/fxtf-drafts/issues/130 [Needs Data] [css-masking-1]
- #197 [css-masking-1] `clip` applies-to section should mention <marker>, not <mask> (1 by dirkschulze)
https://github.com/w3c/fxtf-drafts/issues/197 [Agenda+] [Needs Edits] [Needs SVGWG Input/Decision] [css-masking-1]
- #17 [css-masking] Support <g> element is clipping paths (1 by dirkschulze)
https://github.com/w3c/fxtf-drafts/issues/17 [Needs Data] [css-masking-1]
- #287 Link to fespecularlighting surfaceScale fails linting in SVG spec due to not exporting it in filters spec (1 by dstorey)
https://github.com/w3c/fxtf-drafts/issues/287
1 issues closed:
- Link to fespecularlighting surfaceScale fails linting in SVG spec due to not exporting it in filters spec https://github.com/w3c/fxtf-drafts/issues/287 [Needs Edits] [filter-effects-1]
Pull requests
-------------
* w3c/svgwg (+5/-7/💬10)
5 pull requests submitted:
- Remove defintion of white-space (by dstorey)
https://github.com/w3c/svgwg/pull/464
- Update data-export (by dstorey)
https://github.com/w3c/svgwg/pull/460
- Remove unused defs and fix some linking issues (by dstorey)
https://github.com/w3c/svgwg/pull/458
- Fix issue with MathML namespace and duplicate ID in changelog (by dstorey)
https://github.com/w3c/svgwg/pull/457
- Remove SVGCursorElement... (by dstorey)
https://github.com/w3c/svgwg/pull/455
4 pull requests received 10 new comments:
- #450 Remove solidcolour (4 by dstorey)
https://github.com/w3c/svgwg/pull/450
- #452 Remove mesh gradients (3 by dstorey)
https://github.com/w3c/svgwg/pull/452
- #455 Remove SVGCursorElement... (2 by dstorey, AmeliaBR)
https://github.com/w3c/svgwg/pull/455
- #464 Remove defintion of white-space (1 by dstorey)
https://github.com/w3c/svgwg/pull/464
7 pull requests merged:
- Remove solidcolour
https://github.com/w3c/svgwg/pull/450
- Remove defintion of white-space
https://github.com/w3c/svgwg/pull/464
- Update data-export
https://github.com/w3c/svgwg/pull/460
- Remove unused defs and fix some linking issues
https://github.com/w3c/svgwg/pull/458
- Fix issue with MathML namespace and duplicate ID in changelog
https://github.com/w3c/svgwg/pull/457
- Remove SVGCursorElement...
https://github.com/w3c/svgwg/pull/455
- Remove hatch gradients
https://github.com/w3c/svgwg/pull/451
* w3c/fxtf-drafts (+1/-1/💬2)
1 pull requests submitted:
- Add missing start tag to surfaceScale definition (by dstorey)
https://github.com/w3c/fxtf-drafts/pull/288
1 pull requests received 2 new comments:
- #288 Add missing start tag to surfaceScale definition (2 by dirkschulze, dstorey)
https://github.com/w3c/fxtf-drafts/pull/288
1 pull requests merged:
- Add missing start tag to surfaceScale definition
https://github.com/w3c/fxtf-drafts/pull/288
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, 22 May 2018 17:00:26 UTC