Issues · w3c/svgwg · GitHub

Does the entire path need to be valid in order to use a path attribute on a textPath
#393 · longsonr opened on Mar 20, 2018
16

Labels Milestones New issue

Clarify that `getPathData()` returns the attribute base value, not the CSS resolved/animated value

#1130

· viralipurbey opened

on Jun 10, 2026

`getPathSegmentAtLength()`: Define which segment is returned at exact boundary

#1129

· viralipurbey opened

on Jun 10, 2026

`getPathSegmentAtLength()`: Define behavior for `NaN` distance

#1128

· viralipurbey opened

on Jun 10, 2026

Outline placement on `<tspan>` and other SVG inline text content elements is undefined; engines diverge

#1126

· karlcow opened

on Jun 8, 2026

Clarify `glyph-orientation-vertical` - whether it is obsolete or something need to be kept?

#1122

· Ahmad-S792 opened

on Jun 8, 2026

`text-overflow`: zero-engine support and spec inconsistencies: narrow or drop?

#1115

· karlcow opened

on Jun 2, 2026

space trimming in the context of text/tspan

#1114

· karlcow opened

on May 28, 2026

Behaviour of `:percent` spatial media fragment in SVG when no natural size is given for the external image

#1113

· goldenboy777 opened

on May 21, 2026

16.3.2 fragment grammar vs. implemented handling of `svgView()` combined with `xywh=` (and other disallowed combinations)

#1112

· karlcow opened

on May 20, 2026

chained filter support, aka href on the filter element

#1111

· karlcow opened

on May 20, 2026

`:visited { fill: url(<ref>) <color> }` should the color fallback apply when the URL is suppressed for privacy?

#1107

· karlcow opened

on May 12, 2026

Clarify SMIL animation behavior when path 'd' value is an empty string

#1102

· viralipurbey opened

on Apr 29, 2026