You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
They clearly should be, as my own website uses them frequently and they are part of the HTML spec; they are currently commented out of the list of tags for phrasing contents.
There are two ways of handling this, one expedient and the other more long-term: assume any SVG is fine regardless of its contents and let the browser's renderer attempt to display it, or incorporate a hiccup / malli schema for SVG into the html namespace and use that.
Thinking about how to handle invalid SVG makes me think about the can of 🪱s of invalid HTML more generally: HTML is generally tolerant of partial failures and will still "mostly work" even when elements aren't all in the right place. fabricate should follow this model, but enable optional validation should users desire it.
The text was updated successfully, but these errors were encountered:
They clearly should be, as my own website uses them frequently and they are part of the HTML spec; they are currently commented out of the list of tags for phrasing contents.
There are two ways of handling this, one expedient and the other more long-term: assume any SVG is fine regardless of its contents and let the browser's renderer attempt to display it, or incorporate a
hiccup
/malli
schema for SVG into thehtml
namespace and use that.Thinking about how to handle invalid SVG makes me think about the can of 🪱s of invalid HTML more generally: HTML is generally tolerant of partial failures and will still "mostly work" even when elements aren't all in the right place.
fabricate
should follow this model, but enable optional validation should users desire it.The text was updated successfully, but these errors were encountered: