Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SVG Rendering Changed #54

Open
frogdesk opened this issue Feb 27, 2023 · 3 comments
Open

SVG Rendering Changed #54

frogdesk opened this issue Feb 27, 2023 · 3 comments

Comments

@frogdesk
Copy link

frogdesk commented Feb 27, 2023

Hello,
Previously, SVG based thumbnails were rendered on the front-end, which in most browsers resulted in using the current SVG standard.

However it appears that the new thumbnail rendering method uses an older SVG standard which does not support the transform-origin property.

I was hoping this might be fixable.

Thanks

@SmaugPool
Copy link
Owner

Hi,

Yes, I'm testing the SVG rasterizer which is needed for other purpose (links previews for example).
The plan is to go back to render SVGs natively again in thumbnails once I have identified most issues.

Could you please tell which asset(s) thumbnail is not correctly rendered?

Thank you

@frogdesk
Copy link
Author

frogdesk commented Mar 6, 2023

Glad to hear it :)

Here are a bunch that are not rendering correctly because of transform-origin: https://pool.pm/$wizardcrypt/%40270a4b2c

And here's one that renders correctly, since I replaced the transform-origin in the later mints to minimize this issue: https://pool.pm/$telfire/Wizard%20Spell%2001759

@SmaugPool
Copy link
Owner

@frogdesk SVGs are rendered natively again except in link previews.
So those should now work everywhere except in like previews.

Keeping the issue open until link previews render them correctly too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants