Question about the support for SVG - Vector images? animated SVG? ICON Sets?

[Wolfspyre]

There are other questions too.... but trying to scope each question to one thing 🙂

I'm curious as to the usability of SVGs as images... I make a bunch of icons and logos in vector format; I thought that Chevereto wouldn't have a hard time presenting them as SVG or a quick webp raster with raw svg download option...

I notice that SVG isn't listed in the supported formats list; however there's no mention of SVG / Vectors in the documentation other than the logo.... so.... figured I'd ask.


hope y'all are having a great day!

 

[Rodolfo]

I do believe that Chevereto should at least support all the formats supported by web browsers. That includes SVG 👍

Image file type and format guide - Web media technologies | MDN

In this guide, we'll cover the image file types generally supported by web browsers, and provide insights that will help you select the most appropriate formats to use for your site's imagery.

developer.mozilla.org

 

[Wolfspyre]

okay, cool so its expected that a user SHOULD be able to upload svg images.

is it as simple a change as changing the extension list to not be an exclusive list in the meantime?

i could see handling vector images being a bit cumbersome in unexpected places and needing some contortions to make things work

 

[Rodolfo]

is it as simple a change as changing the extension list

No, it must be remade from scratch. The current implementation lacks extensive validation or parsing for SVG files, as it was originally designed solely for logo editing.

 

[Wolfspyre]

oof.
would it be less, or more work, do you recon, to make a webp/jpg raster of the vector image, and use that in edgecases where, for whatever reason, the vector asset isnt viable?

The thought being that it'd provide a way to gradually roll out vector support to different parts of the app; allowing you to just use the raster variant in lieu of barfing all over the place.... (ie: graceful degradation)
Then again, this could be an absolutely horrible idea 🙂

 

[Rodolfo]

While fallbacks have traditionally been a way to handle situations like this, I don't think they're necessary in this case. SVG support is now widespread across all modern web browsers. The only real concern with SVGs tends to be security-related. Since SVGs are essentially XML documents, they expose a large surface area that can potentially introduce security vulnerabilities, especially if not properly sanitized or handled.

 

[Wolfspyre]

right. hence why the question about a rasterized version....

use a rasterizer sandbox (or potentially convert client-side at upload time?)

and then use the rasterized variant for all codepaths not yet identified as safe?
basically allowing for a less all-or-nothing approach to implementing but ¯\(ツ)/¯