- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 03 Apr 2018 17:00:06 +0000
- To: www-svg@w3.org
- Message-Id: <E1f3PHy-0006S4-1U@uranus.w3.org>
Issues
------
* w3c/svgwg (+10/-3/💬15)
10 issues created:
- Typo in viewBox attribute type definition (by jarek-foksa)
https://github.com/w3c/svgwg/issues/407
- Wrong description of percentage units (by jarek-foksa)
https://github.com/w3c/svgwg/issues/406
- Wrong description of "visibility" property (by jarek-foksa)
https://github.com/w3c/svgwg/issues/405
- Remove "style attributes" from all element definitions (by jarek-foksa)
https://github.com/w3c/svgwg/issues/404
- Replace <opacity-value> with <alpha-value> (by jarek-foksa)
https://github.com/w3c/svgwg/issues/403
- The computed value of fill-opacity stroke-opacity should never be a percentage (by jarek-foksa)
https://github.com/w3c/svgwg/issues/402
- Allow more properties to be applied on <a> inside <text> (by jarek-foksa)
https://github.com/w3c/svgwg/issues/401
- Add <a> to "text content element" category (by jarek-foksa)
https://github.com/w3c/svgwg/issues/400
- Remove "text content child element" category and add <a> to "text content element" category (by jarek-foksa)
https://github.com/w3c/svgwg/issues/399
- "mode" of a shadow root which <use> element uses is unclear (by hayatoito)
https://github.com/w3c/svgwg/issues/396
10 issues received 15 new comments:
- #400 Add <a> to "text content element" category (4 by longsonr, jarek-foksa)
https://github.com/w3c/svgwg/issues/400
- #396 "mode" of a shadow root which <use> element uses is unclear (2 by hayatoito, AmeliaBR)
https://github.com/w3c/svgwg/issues/396
- #402 The computed value of fill-opacity and stroke-opacity should never be a percentage (2 by longsonr, AmeliaBR)
https://github.com/w3c/svgwg/issues/402
- #362 Convert SVG linking reftests to .svg files (1 by heycam)
https://github.com/w3c/svgwg/issues/362 [Linking chapter] [Needs tests]
- #175 Make SVGAnimatedX data types extend DOMX data types wherever possible (1 by dstorey)
https://github.com/w3c/svgwg/issues/175 [Basic Data Types and Interfaces chapter] [Future wish list] [Needs WG input] [SVG Core]
- #242 Cut down number of categories (1 by jarek-foksa)
https://github.com/w3c/svgwg/issues/242 [Entire spec] [Needs WG input] [SVG Core]
- #403 Replace <opacity-value> with <alpha-value> (1 by AmeliaBR)
https://github.com/w3c/svgwg/issues/403 [Appendices] [Painting chapter] [SVG Core]
- #399 Remove "text content child element" category (1 by jarek-foksa)
https://github.com/w3c/svgwg/issues/399
- #405 Wrong description of "visibility" property (1 by AmeliaBR)
https://github.com/w3c/svgwg/issues/405 [Document structure chapter] [Rendering Model chapter] [SVG Core]
- #312 SVGAElement implements two conflicting interfaces (1 by dstorey)
https://github.com/w3c/svgwg/issues/312 [Linking chapter] [SVG Core]
3 issues closed:
- "mode" of a shadow root which <use> element uses is unclear https://github.com/w3c/svgwg/issues/396
- Remove "text content child element" category https://github.com/w3c/svgwg/issues/399
- Add <a> to "text content element" category https://github.com/w3c/svgwg/issues/400
* w3c/svg-aam (+1/-0/💬5)
1 issues created:
- Fix issues with mapping script (by AmeliaBR)
https://github.com/w3c/svg-aam/issues/10 [Bug (in spec/tools)] [Needs ARIA WG Input]
1 issues received 5 new comments:
- #3 Prepare new working draft (February 2018) (5 by svgeesus, AmeliaBR)
https://github.com/w3c/svg-aam/issues/3 [Needs Edits]
* w3c/fxtf-drafts (+1/-0/💬1)
1 issues created:
- [css-masking-1][filter-effects] Update definitions to take into account that `<use>` element is no longer a graphics element in SVG 2 (by jarek-foksa)
https://github.com/w3c/fxtf-drafts/issues/266
1 issues received 1 new comments:
- #111 [css-masking] Change initial value of mask-repeat and mask-position (1 by csnardi)
https://github.com/w3c/fxtf-drafts/issues/111 [Needs Edits] [css-masking-1]
* w3c/graphics-aria (+1/-0/💬1)
1 issues created:
- Redundant use of 'instead' in graphics-object spec (by carmacleod)
https://github.com/w3c/graphics-aria/issues/4
1 issues received 1 new comments:
- #4 Redundant use of 'instead' in graphics-object spec (1 by AmeliaBR)
https://github.com/w3c/graphics-aria/issues/4
Pull requests
-------------
* w3c/svgwg (+2/-2/💬9)
2 pull requests submitted:
- Remove support for segment-completing close path (by ewilligers)
https://github.com/w3c/svgwg/pull/398
- Remove path rotation requirement (by ewilligers)
https://github.com/w3c/svgwg/pull/397
7 pull requests received 9 new comments:
- #398 Remove support for segment-completing close path (2 by ewilligers, css-meeting-bot)
https://github.com/w3c/svgwg/pull/398
- #251 Add text-transform property to the list of required CSS properties (2 by boggydigital, css-meeting-bot)
https://github.com/w3c/svgwg/pull/251 [Needs WG input] [SVG Core] [Styling chapter] [Text chapter]
- #376 Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 (1 by dstorey)
https://github.com/w3c/svgwg/pull/376
- #374 'd' presentation attribute: use path() function (1 by css-meeting-bot)
https://github.com/w3c/svgwg/pull/374 [Basic shapes chapter] [Geometry Properties chapter] [Needs WG input]
- #311 Change SVGMeshElement to derive from SVGGraphicsElement (1 by css-meeting-bot)
https://github.com/w3c/svgwg/pull/311
- #346 Fixed path grammar (1 by css-meeting-bot)
https://github.com/w3c/svgwg/pull/346
- #158 Revisions to sentence on focusable elements (1 by css-meeting-bot)
https://github.com/w3c/svgwg/pull/158
2 pull requests merged:
- Revisions to sentence on focusable elements
https://github.com/w3c/svgwg/pull/158
- Remove path rotation requirement
https://github.com/w3c/svgwg/pull/397
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, 3 April 2018 17:00:15 UTC