Event JSON
{
"id": "8a63d77ba3a79f8b58a9f3696d1b6bfb96428c9b9815c0f5b473b6c88be4ae45",
"pubkey": "effca4793b2710c9d391f2af243fc7228b446437e13c605b2ee931d03319336f",
"created_at": 1716047851,
"kind": 1,
"tags": [
[
"t",
"svg"
],
[
"t",
"stateofhtml"
],
[
"proxy",
"https://front-end.social/@leaverou/112462911996321322",
"web"
],
[
"proxy",
"https://front-end.social/users/leaverou/statuses/112462911996321322",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://front-end.social/users/leaverou/statuses/112462911996321322",
"pink.momostr"
]
],
"content": "We’ve always told devs that browsers prioritize what to implement based on dev demand.\n\nThere is one exception: #SVG. \n\nSVG is used on \u003e65% of websites. Yet, browsers have been *refusing* to work on SVG, ignoring pressure and pain points from web devs.\n\n#StateOfHTML showed SVG as the top content pain point: https://2023.stateofhtml.com/en-US/features/content/#content_pain_points\n\nTons of work (SVG 2, fill \u0026 stroke, and more) has sat unimplemented for years. At this point, in standards circles, we know not to touch SVG with a barge pole.\n\n[1/2]",
"sig": "46aadf4b61019dc7a2c2ab6ab0168633f1c31f38d78bb49ce8595413eb63e66f2798511f0ca681d4e6b5143ddcfec655f9067cfad4d81914c8acddc4aaed3b44"
}