What's missing from SVG

SVG is very cool for displaying graphics on the web but, like any web technology, there's always more we could be doing with it, whether it's fixing bugs and browser inconsistencies, adding new features to unlock new use cases, or improving performance. I wanted to learn more, so I asked around and analyzed a few different sources of developer signals on the topic. Here are the sources I used: SVG tickets from the Chromium bug tracker. Interop focus area proposals about SVG. Comments left on the "SVG issues" response to the graphics pain points question in the State of CSS 2025 survey. Free-form responses to a question I asked on social media. What's missing from SVG - The short version Here's the short version of what web developers feel is missing from SVG: Styling and theming external SVG assets Developers want SVGs used via <img>, background-image, favicons, and sprites to be as styleable as inline SVGs: pass theme values, use currentColor and custom properties, without…