Re: [svgwg] <Image> auto-rotation due to 'Orientation' attribute in EXIF Data (#819)
- Re: [svgwg] <Image> auto-rotation due to 'Orientation' attribute in EXIF Data (#819)
- Re: [svgwg] <Image> auto-rotation due to 'Orientation' attribute in EXIF Data (#819)
[svgwg] Issue: Clarify `glyph-orientation-vertical` - whether it is obsolete or something need to be kept? (#1122) marked as Agenda+
Closed: [svgwg] Clarify that SVG does not need to be valid XML (#960)
Re: [svgwg] Clarify that SVG does not need to be valid XML (#960)
[svgwg] Issue: Clarify that `getPathData()` returns the attribute base value, not the CSS resolved/animated value (#1130) marked as Agenda+
[svgwg] Clarify that `getPathData()` returns the attribute base value, not the CSS resolved/animated value (#1130)
- Re: [svgwg] Clarify that `getPathData()` returns the attribute base value, not the CSS resolved/animated value (#1130)
- Re: [svgwg] Clarify that `getPathData()` returns the attribute base value, not the CSS resolved/animated value (#1130)
[svgwg] `getPathSegmentAtLength()`: Define which segment is returned at exact boundary (#1129)
- Re: [svgwg] `getPathSegmentAtLength()`: Define which segment is returned at exact boundary (#1129)
- Re: [svgwg] `getPathSegmentAtLength()`: Define which segment is returned at exact boundary (#1129)
[svgwg] Issue: `getPathSegmentAtLength()`: Define which segment is returned at exact boundary (#1129) marked as Agenda+
[svgwg] `getPathSegmentAtLength()`: Define behavior for `NaN` distance (#1128)
- Re: [svgwg] `getPathSegmentAtLength()`: Define behavior for `NaN` distance (#1128)
- Re: [svgwg] `getPathSegmentAtLength()`: Define behavior for `NaN` distance (#1128)
[svgwg] Issue: `getPathSegmentAtLength()`: Define behavior for `NaN` distance (#1128) marked as Agenda+
[svgwg] Pull Request: fix IDL exclusion
Re: [svgwg] [SVG] standalone or not ? (#1088)
[svgwg] Merged Pull Request: Clarify that SVG requires well-formed XML, not valid XML
Re: [svgwg] The value definition of `path-length` is broken (#1101)
[svgwg] Outline placement on `<tspan>` and other SVG inline text content elements is undefined; engines diverge (#1126)
[svgwg] Pull Request: Fix #1124 - broken links and warnings in build output
[svgwg] [editorial] Fix build issues showed by the make command (#1124)
Re: [svgwg] Clarify that SVG requires well-formed XML, not valid XML (#1109)
- Re: [svgwg] Clarify that SVG requires well-formed XML, not valid XML (#1109)
- Re: [svgwg] Clarify that SVG requires well-formed XML, not valid XML (#1109)
[svgwg] 🤖 Featured on pcell.si — AI agents are reviewing this repo (#1123)
[svgwg] Clarify `glyph-orientation-vertical` - whether it is obsolete or something need to be kept? (#1122)
- Re: [svgwg] Clarify `glyph-orientation-vertical` - whether it is obsolete or something need to be kept? (#1122)
- Re: [svgwg] Clarify `glyph-orientation-vertical` - whether it is obsolete or something need to be kept? (#1122)
- Re: [svgwg] Clarify `glyph-orientation-vertical` - whether it is obsolete or something need to be kept? (#1122)
[svgwg] Pull Request: fix #1119 - fix typo in the circle IDL prose.
[svgwg] Pull Request: Fix circle r property reference
- [svgwg] Closed Pull Request: Fix circle r property reference
- Re: [svgwg] Fix circle r property reference (#1120)
[svgwg] typo: fix the enumeration of attributes in 10.8.2 (#1119)
[svgwg] Pull Request: Change path-length property value type from number to length
- Re: [svgwg] Change path-length property value type from number to length (#1118)
- [svgwg] Merged Pull Request: Change path-length property value type from number to length
[svgwg] Pull Request: updates SVG2 to comply to the process 2025 wording requirements
- Re: [svgwg] updates SVG2 to comply to the process 2025 wording requirements (#1117)
- Re: [svgwg] updates SVG2 to comply to the process 2025 wording requirements (#1117)
- Re: [svgwg] updates SVG2 to comply to the process 2025 wording requirements (#1117)
- Re: [svgwg] updates SVG2 to comply to the process 2025 wording requirements (#1117)
- [svgwg] Merged Pull Request: updates SVG2 to comply to the process 2025 wording requirements
- Re: [svgwg] updates SVG2 to comply to the process 2025 wording requirements (#1117)
Re: [svgwg] 16.3.2 fragment grammar vs. implemented handling of `svgView()` combined with `xywh=` (and other disallowed combinations) (#1112)
Re: [svgwg] Behaviour of `:percent` spatial media fragment in SVG when no natural size is given for the external image (#1113)
Re: [svgwg] space trimming in the context of text/tspan (#1114)
- Re: [svgwg] space trimming in the context of text/tspan (#1114)
- Re: [svgwg] space trimming in the context of text/tspan (#1114)
- Re: [svgwg] space trimming in the context of text/tspan (#1114)
- Re: [svgwg] space trimming in the context of text/tspan (#1114)
[svgwg] Pull Request: Fix swapped href targets for open/closed subpath terms in definitions.xml
- Re: [svgwg] Fix swapped href targets for open/closed subpath terms in definitions.xml (#1116)
- [svgwg] Merged Pull Request: Fix swapped href targets for open/closed subpath terms in definitions.xml