public-svg-issues@w3.org from June 2026 by author

Ahmad Saleem via GitHub

• [svgwg] Clarify `glyph-orientation-vertical` - whether it is obsolete or something need to be kept? (#1122) (Monday, 8 June)

caribouW3 via GitHub

• [svgwg] Specification of a new fragment identifier for the image/svg+xml media type (for use with CSS Linked Parameters) (#1144) (Monday, 29 June)
• [svgwg] Merged Pull Request: updates SVG2 to comply to the process 2025 wording requirements (Monday, 8 June)

Class 1 Critical Unforeseen Weapon via GitHub

• [svgwg] 🤖 Featured on pcell.si — AI agents are reviewing this repo (#1123) (Monday, 8 June)

Denis Ah-Kang via GitHub

• [svgwg] Pull Request: fix IDL exclusion (Tuesday, 9 June)
• Re: [svgwg] updates SVG2 to comply to the process 2025 wording requirements (#1117) (Monday, 8 June)
• Re: [svgwg] updates SVG2 to comply to the process 2025 wording requirements (#1117) (Monday, 8 June)
• [svgwg] Pull Request: updates SVG2 to comply to the process 2025 wording requirements (Thursday, 4 June)

Dirk Schulze via GitHub

• Re: [svgwg] Define how `requiredExtensions` values should be interpreted (#138) (Thursday, 25 June)
• Re: [svgwg] refX/refY keyword forms unimplemented and no WPT tests (#1137) (Thursday, 25 June)
• Re: [svgwg] refX/refY keyword forms unimplemented and no WPT tests (#1137) (Thursday, 18 June)
• Re: [svgwg] 'Segment-completing close path operation' command not implemented (#893) (Thursday, 18 June)
• Re: [svgwg] <Image> auto-rotation due to 'Orientation' attribute in EXIF Data (#819) (Thursday, 11 June)
• Re: [svgwg] Clarify `glyph-orientation-vertical` - whether it is obsolete or something need to be kept? (#1122) (Thursday, 11 June)
• Re: [svgwg] `getPathSegmentAtLength()`: Define behavior for `NaN` distance (#1128) (Thursday, 11 June)
• Re: [svgwg] `getPathSegmentAtLength()`: Define which segment is returned at exact boundary (#1129) (Thursday, 11 June)
• Re: [svgwg] Clarify that `getPathData()` returns the attribute base value, not the CSS resolved/animated value (#1130) (Thursday, 11 June)
• Re: [svgwg] 16.3.2 fragment grammar vs. implemented handling of `svgView()` combined with `xywh=` (and other disallowed combinations) (#1112) (Thursday, 4 June)
• Re: [svgwg] Behaviour of `:percent` spatial media fragment in SVG when no natural size is given for the external image (#1113) (Thursday, 4 June)
• Re: [svgwg] space trimming in the context of text/tspan (#1114) (Thursday, 4 June)

Divyansh Mangal via GitHub

• [svgwg] Issue: Media fragment percent fallback should reference css-images-3 default object size instead of CSS 2.1 (#1136) marked as Agenda+ (Friday, 19 June)
• [svgwg] Media fragment percent fallback should reference css-images-3 default object size instead of CSS 2.1 (#1136) (Tuesday, 16 June)
• Re: [svgwg] space trimming in the context of text/tspan (#1114) (Thursday, 4 June)

François Daoust via GitHub

• Re: [svgwg] updates SVG2 to comply to the process 2025 wording requirements (#1117) (Tuesday, 9 June)

Guillaume via GitHub

• Re: [svgwg] The value definition of `path-length` is broken (#1101) (Tuesday, 9 June)

herrstrietzel via GitHub

• Re: [svgwg] `getPathSegmentAtLength()`: Define which segment is returned at exact boundary (#1129) (Wednesday, 17 June)

Jofdt via GitHub

• Re: [svgwg] Filter Effects: define interoperable backdrop displacement/refraction for “liquid glass” UI (#1142) (Thursday, 25 June)
• Re: [svgwg] Filter Effects: define interoperable backdrop displacement/refraction for “liquid glass” UI (#1142) (Thursday, 25 June)
• [svgwg] Filter Effects: define interoperable backdrop displacement/refraction for “liquid glass” UI (#1142) (Thursday, 25 June)

Kaj Kowalski via GitHub

• [svgwg] Pull Request: Fix swapped href targets for open/closed subpath terms in definitions.xml (Thursday, 4 June)

Karl Dubost via GitHub

• Re: [svgwg] Revert change from SVGRect/SVGPoint/SVGMatrix to DOM equivalents (#706) (Monday, 29 June)
• [svgwg] Pull Request: Revert SVG*→DOM* geometry-interface aliasing (#706) (Monday, 29 June)
• [svgwg] Pull Request: Revert SVG*→DOM* geometry-interface aliasing (#706) (Monday, 29 June)
• [svgwg] Issue: Remove instanceRoot and animatedInstanceRoot? (#852) marked as Agenda+ (Sunday, 28 June)
• Re: [svgwg] Remove instanceRoot and animatedInstanceRoot? (#852) (Sunday, 28 June)
• Re: [svgwg] `getPathSegmentAtLength()`: Define which segment is returned at exact boundary (#1129) (Thursday, 25 June)
• Closed: [svgwg] `getPathSegmentAtLength()`: Define which segment is returned at exact boundary (#1129) (Thursday, 25 June)
• [svgwg] Merged Pull Request: Define `getPathSegmentAtLength()` behavior at segment boundary (Thursday, 25 June)
• Closed: [svgwg] `getPathSegmentAtLength()`: Define behavior for `NaN` distance (#1128) (Thursday, 25 June)
• [svgwg] Merged Pull Request: Define `getPathSegmentAtLength()` behavior for `NaN` distance (Thursday, 25 June)
• Closed: [svgwg] Clarify that `getPathData()` returns the attribute base value, not the CSS resolved/animated value (#1130) (Thursday, 25 June)
• [svgwg] Merged Pull Request: Clarify that `getPathData()` returns the attribute base value (Thursday, 25 June)
• Re: [svgwg] Clarify that SVG requires well-formed XML, not valid XML (#1109) (Tuesday, 23 June)
• Re: [svgwg] Clarify that SVG requires well-formed XML, not valid XML (#1109) (Tuesday, 23 June)
• [svgwg] Merged Pull Request: Improve #960 pr with simpler phrasing. (Tuesday, 23 June)
• Re: [svgwg] Improve #960 pr with simpler phrasing. (#1141) (Tuesday, 23 June)
• [svgwg] Pull Request: Improve #960 pr with simpler phrasing. (Tuesday, 23 June)
• [svgwg] Issue: Clean up glyph-orientation-vertical and glyph-orientation-vertical from the spec. (#1140) marked as Needs removal (Tuesday, 23 June)
• [svgwg] Clean up glyph-orientation-vertical and glyph-orientation-vertical from the spec. (#1140) (Tuesday, 23 June)
• Re: [svgwg] Define how `requiredExtensions` values should be interpretted (#138) (Friday, 19 June)
• [svgwg] Issue: Define how `requiredExtensions` values should be interpretted (#138) marked as Agenda+ (Friday, 19 June)
• Closed: [svgwg] 'Segment-completing close path operation' command not implemented (#893) (Thursday, 18 June)
• [svgwg] Merged Pull Request: fix #893 - drop section about completion of segments. (Thursday, 18 June)
• [svgwg] Pull Request: fix #893 - drop section about completion of segments. (Thursday, 18 June)
• Re: [svgwg] refX/refY keyword forms unimplemented and no WPT tests (#1137) (Thursday, 18 June)
• Re: [svgwg] refX/refY keyword forms unimplemented and no WPT tests (#1137) (Thursday, 18 June)
• Re: [svgwg] 'Segment-completing close path operation' command not implemented (#893) (Thursday, 18 June)
• Re: [svgwg] refX/refY keyword forms unimplemented and no WPT tests (#1137) (Wednesday, 17 June)
• [svgwg] Issue: refX/refY keyword forms unimplemented and no WPT tests (#1137) marked as Agenda+ (Wednesday, 17 June)
• [svgwg] refX/refY keyword forms unimplemented and no WPT tests (#1137) (Wednesday, 17 June)
• Closed: [svgwg] [editorial] Links to the current version of the specifications. (#1131) (Monday, 15 June)
• [svgwg] Merged Pull Request: #1131 - fixing links to the current versions of specifications (Monday, 15 June)
• [svgwg] Pull Request: #1131 - fixing links to the current versions of specifications (Monday, 15 June)
• [svgwg] [editorial] Links to the current version of the specifications. (#1131) (Monday, 15 June)
• Re: [svgwg] space trimming in the context of text/tspan (#1114) (Thursday, 11 June)
• Re: [svgwg] Clarify `glyph-orientation-vertical` - whether it is obsolete or something need to be kept? (#1122) (Thursday, 11 June)
• Re: [svgwg] `getPathSegmentAtLength()`: Define which segment is returned at exact boundary (#1129) (Thursday, 11 June)
• Re: [svgwg] Clarify that `getPathData()` returns the attribute base value, not the CSS resolved/animated value (#1130) (Thursday, 11 June)
• Re: [svgwg] `getPathSegmentAtLength()`: Define behavior for `NaN` distance (#1128) (Thursday, 11 June)
• Re: [svgwg] space trimming in the context of text/tspan (#1114) (Thursday, 11 June)
• [svgwg] Issue: Clarify `glyph-orientation-vertical` - whether it is obsolete or something need to be kept? (#1122) marked as Agenda+ (Thursday, 11 June)
• Closed: [svgwg] Clarify that SVG does not need to be valid XML (#960) (Wednesday, 10 June)
• [svgwg] Merged Pull Request: fix IDL exclusion (Tuesday, 9 June)
• [svgwg] Merged Pull Request: Clarify that SVG requires well-formed XML, not valid XML (Tuesday, 9 June)
• [svgwg] Outline placement on `<tspan>` and other SVG inline text content elements is undefined; engines diverge (#1126) (Monday, 8 June)
• Closed: [svgwg] 🤖 Featured on pcell.si — AI agents are reviewing this repo (#1123) (Monday, 8 June)
• Re: [svgwg] updates SVG2 to comply to the process 2025 wording requirements (#1117) (Monday, 8 June)
• Closed: [svgwg] [editorial] Fix build issues showed by the make command (#1124) (Monday, 8 June)
• [svgwg] Merged Pull Request: Fix #1124 - broken links and warnings in build output (Monday, 8 June)
• [svgwg] Pull Request: Fix #1124 - broken links and warnings in build output (Monday, 8 June)
• [svgwg] [editorial] Fix build issues showed by the make command (#1124) (Monday, 8 June)
• Re: [svgwg] Clarify that SVG requires well-formed XML, not valid XML (#1109) (Monday, 8 June)
• [svgwg] Merged Pull Request: Fix swapped href targets for open/closed subpath terms in definitions.xml (Monday, 8 June)
• Re: [svgwg] updates SVG2 to comply to the process 2025 wording requirements (#1117) (Monday, 8 June)
• Re: [svgwg] Fix circle r property reference (#1120) (Monday, 8 June)
• [svgwg] Closed Pull Request: Fix circle r property reference (Monday, 8 June)
• [svgwg] Merged Pull Request: Change path-length property value type from number to length (Monday, 8 June)
• Closed: [svgwg] typo: fix the enumeration of attributes in 10.8.2 for circle element (#1119) (Sunday, 7 June)
• [svgwg] Merged Pull Request: fix #1119 - fix typo in the circle IDL prose. (Sunday, 7 June)
• [svgwg] Pull Request: fix #1119 - fix typo in the circle IDL prose. (Sunday, 7 June)
• [svgwg] typo: fix the enumeration of attributes in 10.8.2 (#1119) (Sunday, 7 June)
• Re: [svgwg] Behaviour of `:percent` spatial media fragment in SVG when no natural size is given for the external image (#1113) (Thursday, 4 June)
• [svgwg] `text-overflow`: zero-engine support and spec inconsistencies: narrow or drop? (#1115) (Tuesday, 2 June)

Nikolas Zimmermann via GitHub

• Re: [svgwg] refX/refY keyword forms unimplemented and no WPT tests (#1137) (Thursday, 18 June)
• Re: [svgwg] <Image> auto-rotation due to 'Orientation' attribute in EXIF Data (#819) (Thursday, 11 June)
• Re: [svgwg] <Image> auto-rotation due to 'Orientation' attribute in EXIF Data (#819) (Thursday, 11 June)

Peter Krautzberger via GitHub

• [svgwg] transform on nested svg (#1139) (Friday, 19 June)
• Re: [svgwg] Outline placement on `<tspan>` and other SVG inline text content elements is undefined; engines diverge (#1126) (Monday, 8 June)

Robert Longson via GitHub

• Re: [svgwg] Filter Effects: define interoperable backdrop displacement/refraction for “liquid glass” UI (#1142) (Thursday, 25 June)
• Re: [svgwg] Filter Effects: define interoperable backdrop displacement/refraction for “liquid glass” UI (#1142) (Thursday, 25 June)
• Re: [svgwg] Clarify `glyph-orientation-vertical` - whether it is obsolete or something need to be kept? (#1122) (Monday, 8 June)

sideshowbarker via GitHub

• [svgwg] Merged Pull Request: Revert SVG*→DOM* geometry-interface aliasing (#706) (Monday, 29 June)

Stephen Chenney via GitHub

• Re: [svgwg] <Image> auto-rotation due to 'Orientation' attribute in EXIF Data (#819) (Thursday, 11 June)

Tavmjong via GitHub

• Re: [svgwg] refX/refY keyword forms unimplemented and no WPT tests (#1137) (Thursday, 25 June)
• Re: [svgwg] space trimming in the context of text/tspan (#1114) (Thursday, 11 June)

titanniya542-spec via GitHub

• [svgwg] Pull Request: Fix circle r property reference (Sunday, 7 June)

viralipurbey via GitHub

• Re: [svgwg] Define `getPathSegmentAtLength()` behavior for `NaN` distance (#1133) (Wednesday, 17 June)
• Re: [svgwg] Define `getPathSegmentAtLength()` behavior at segment boundary (#1134) (Wednesday, 17 June)
• Re: [svgwg] Clarify that `getPathData()` returns the attribute base value (#1135) (Wednesday, 17 June)
• [svgwg] Issue: 'Segment-completing close path operation' command not implemented (#893) marked as Agenda+ (Wednesday, 17 June)
• [svgwg] Pull Request: Clarify that `getPathData()` returns the attribute base value (Tuesday, 16 June)
• [svgwg] Pull Request: Define `getPathSegmentAtLength()` behavior at segment boundary (Tuesday, 16 June)
• [svgwg] Pull Request: Define `getPathSegmentAtLength()` behavior for `NaN` distance (Tuesday, 16 June)
• [svgwg] Issue: Clarify that `getPathData()` returns the attribute base value, not the CSS resolved/animated value (#1130) marked as Agenda+ (Wednesday, 10 June)
• [svgwg] Clarify that `getPathData()` returns the attribute base value, not the CSS resolved/animated value (#1130) (Wednesday, 10 June)
• [svgwg] `getPathSegmentAtLength()`: Define which segment is returned at exact boundary (#1129) (Wednesday, 10 June)
• [svgwg] Issue: `getPathSegmentAtLength()`: Define which segment is returned at exact boundary (#1129) marked as Agenda+ (Wednesday, 10 June)
• [svgwg] `getPathSegmentAtLength()`: Define behavior for `NaN` distance (#1128) (Wednesday, 10 June)
• [svgwg] Issue: `getPathSegmentAtLength()`: Define behavior for `NaN` distance (#1128) marked as Agenda+ (Wednesday, 10 June)
• Re: [svgwg] Change path-length property value type from number to length (#1118) (Friday, 5 June)
• [svgwg] Pull Request: Change path-length property value type from number to length (Friday, 5 June)

vlakoff via GitHub

• Re: [svgwg] [SVG] standalone or not ? (#1088) (Thursday, 11 June)
• Re: [svgwg] Clarify that SVG does not need to be valid XML (#960) (Wednesday, 10 June)
• Re: [svgwg] [SVG] standalone or not ? (#1088) (Tuesday, 9 June)
• Re: [svgwg] Clarify that SVG requires well-formed XML, not valid XML (#1109) (Monday, 8 June)

W3C Bot via GitHub

• Re: [svgwg] Clarify that SVG requires well-formed XML, not valid XML (#1109) (Monday, 8 June)
• Re: [svgwg] Fix swapped href targets for open/closed subpath terms in definitions.xml (#1116) (Thursday, 4 June)

Yehonatan Daniv via GitHub

• Re: [svgwg] Define how `requiredExtensions` values should be interpreted (#138) (Thursday, 25 June)

Last message date: Monday, 29 June 2026 14:28:34 UTC