-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
[Proposal] Keep/add xmlns
attribute for generated SVG images
#23409
Comments
Yes it would be welcome to add |
Actually I misread. You are talking about SVG assets, I'm talking about user content SVG image rendering.
|
Yup, for rendering, they do not need the xmlns. We can remove the attribute before rendering, how do you think? |
The PR: Keep/add xmlns attribute for generated SVG images #23410 The output is still clear, and developers could understand/choose SVG images quickly. |
…23410) Fix #23409 Developers could browse & preview the local SVG images files directly. It still has clear output. ![image](https://user-images.githubusercontent.com/2114189/224317107-f4b26c76-e36a-4e80-9eee-d8dc2e16421f.png) ![image](https://user-images.githubusercontent.com/2114189/224317527-2d4ca131-978c-4933-b071-4bae483f06e1.png) --------- Co-authored-by: silverwind <[email protected]> Co-authored-by: delvh <[email protected]>
Feature Description
Gitea's SVG files do not have the
xmlns
attribute. Without it, these SVG images couldn't be display correctly.Then developers couldn't browse these images, they couldn't know what the images look like before rendering them as inline SVG in a page.
So it's better to keep/add the
xmlns
attribute for the generated SVG files.https://stackoverflow.com/questions/18467982/are-svg-parameters-such-as-xmlns-and-version-needed
cc @silverwind
Screenshots
The text was updated successfully, but these errors were encountered: