leaverou , 1 month ago We’ve always told devs that browsers prioritize what to implement based on dev 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: https://2023.stateofhtml.com/en-US/features/content/#content_pain_points 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. [1/2]
We’ve always told devs that browsers prioritize what to implement based on dev 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: https://2023.stateofhtml.com/en-US/features/content/#content_pain_points
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.
[1/2]
