We’ve always told web devs that browsers prioritize what to implement based on developer demand. There is one exception: SVG. SVG is used on >65% of websites. Yet, browsers have been *refusing* to work on SVG, ignoring pressure and pain points from web devs. #StateOfHTML showed SVG as the top content pain point: 2023.stateofhtml.com/en-US/f… Tons of work (SVG 2, fill & stroke, and more) has sat unimplemented for years. At this point, in standards circles, we know not to touch SVG with a barge pole. Case that prompted this post, Custom SVG elements. 7y of pressure, a cornucopia of use cases, yet “no implementer interest”: github.com/WICG/webcomponent… Can someone shed some light on why browsers are so desperate to kill SVG? Because at this point, I refuse to believe this is just a rational business decision based on hard facts. The hard facts are shouting “Fix your damn implementations!” and browsers are going "la-la-la" 🙉🙉🙉