• Welcome to the Chevereto user community!

    Here users from all over the world gather around to learn the latest about Chevereto and contribute with ideas to improve the software.

    Please keep in mind:

    • This community is user driven. Be polite with other users.
    • Is required to purchase a Chevereto license to participate in this community (doesn't apply to Pre-sales).
    • Purchase a Pro Subscription to get access to active software support and faster ticket response times.

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

Wolfspyre

Wolfspyre

Chevereto Member
Pro
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!
 
Sort by date Sort by votes
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
 
Upvote 0 Downvote
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 🙂
 
Upvote 0 Downvote
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.
 
Upvote 0 Downvote
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 ¯\(ツ)/¯
 
Upvote 0 Downvote
You must log in or register to reply here.
Back
Top