I proposed a general SVG focus area two years ago and it got some interest but the feedback was that it was too big and unfocused. This year I want to try again with a more scoped proposal with specific areas we have reason to believe are significant pain points for devs.

• Allow omission of fragment when using SVG <use>
  • Proposed last year: https://github.com/web-platform-tests/interop/issues/1045 , got 23 👍🏻
  • Spec: https://w3c.github.io/svgwg/svg2-draft/linking.html#SVGFragmentIdentifiers
  • WPT: https://wpt.fyi/results/svg/struct/reftests/use-external-svg-resource-no-fragment-id.html
• Support context-fill and context-stroke to make SVGs more easily themeable (reuse context colors in <marker> and <use> elements)
  • WPT: https://wpt.fyi/results/?label=experimental&label=master&aligned&q=feature%3Acontext-fill-stroke
  • Spec: https://w3c.github.io/svgwg/svg2-draft/painting.html
• SVG filters
  • Proposed for Interop 25 https://github.com/web-platform-tests/interop/issues/756 got 52 👍🏻.
  • They allow devs to achieve a lot of effects that otherwise involve content duplication or using external images or JS.
  • Spec: https://drafts.csswg.org/filter-effects-1/
  • WPT: https://wpt.fyi/results/css/filter-effects?label=master&label=experimental&aligned&q=%21backdrop-filter
• getPathData()/setPathData()/getPathSegmentAtLength()/SVGPathElement
  • These grant web developers working with SVG paths a programmatic way to inspect or manipulate individual path segments. Today devs rely on polyfills for this, like this one that has 130 stars: https://github.com/jarek-foksa/path-data-polyfill. The crbug asking for this has positive dev feedback and 44 +1s.
  • Spec: https://w3c.github.io/svgwg/specs/paths/#DOMInterfaces
  • WPT: https://wpt.fyi/results/svg/path/interfaces?label=experimental&label=master&aligned