- From: W3C Webmaster via GitHub API <noreply@w3.org>
- Date: Tue, 16 Jun 2026 17:00:52 +0000
- To: www-svg@w3.org
- Message-ID: <178162925237.1515306.9142065954913445566@janus.w3.internal>
Issues
------
* w3c/svgwg (+4/-2/💬17)
4 issues created:
- [editorial] Links to the current version of the specifications. (by karlcow)
https://github.com/w3c/svgwg/issues/1131
- Clarify that `getPathData()` returns the attribute base value, not the CSS resolved/animated value (by viralipurbey)
https://github.com/w3c/svgwg/issues/1130
- `getPathSegmentAtLength()`: Define which segment is returned at exact boundary (by viralipurbey)
https://github.com/w3c/svgwg/issues/1129
- `getPathSegmentAtLength()`: Define behavior for `NaN` distance (by viralipurbey)
https://github.com/w3c/svgwg/issues/1128
8 issues received 17 new comments:
- #1130 Clarify that `getPathData()` returns the attribute base value, not the CSS resolved/animated value (2 by dirkschulze, karlcow)
https://github.com/w3c/svgwg/issues/1130
- #1129 `getPathSegmentAtLength()`: Define which segment is returned at exact boundary (2 by dirkschulze, karlcow)
https://github.com/w3c/svgwg/issues/1129
- #1128 `getPathSegmentAtLength()`: Define behavior for `NaN` distance (2 by dirkschulze, karlcow)
https://github.com/w3c/svgwg/issues/1128
- #1122 Clarify `glyph-orientation-vertical` - whether it is obsolete or something need to be kept? (2 by dirkschulze, karlcow)
https://github.com/w3c/svgwg/issues/1122
- #1114 space trimming in the context of text/tspan (3 by Tavmjong, karlcow)
https://github.com/w3c/svgwg/issues/1114
- #1088 [SVG] standalone or not ? (1 by vlakoff)
https://github.com/w3c/svgwg/issues/1088
- #960 Clarify that SVG does not need to be valid XML (1 by vlakoff)
https://github.com/w3c/svgwg/issues/960
- #819 <Image> auto-rotation due to 'Orientation' attribute in EXIF Data (4 by dirkschulze, nikolaszimmermann, schenney-chromium)
https://github.com/w3c/svgwg/issues/819
2 issues closed:
- [editorial] Links to the current version of the specifications. https://github.com/w3c/svgwg/issues/1131
- Clarify that SVG does not need to be valid XML https://github.com/w3c/svgwg/issues/960
Pull requests
-------------
* w3c/svgwg (+4/-0/💬0)
4 pull requests submitted:
- 1135 (by viralipurbey)
https://github.com/w3c/svgwg/pull/1135
- 1134 (by viralipurbey)
https://github.com/w3c/svgwg/pull/1134
- 1133 (by viralipurbey)
https://github.com/w3c/svgwg/pull/1133
- 1132 (by karlcow)
https://github.com/w3c/svgwg/pull/1132
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, 16 June 2026 17:00:53 UTC