-
-
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
SVGs should always have the option to be displayed as image #14943
Labels
issue/duplicate
The issue has already been reported.
Comments
Look I don't think this is a bug - it's a missing feature. |
zeripath
changed the title
[Bug] SVGs should always have the option to be displayed as image
SVGs should always have the option to be displayed as image
Mar 11, 2021
zeripath
added
type/feature
Completely new functionality. Can only be merged if feature freeze is not active.
topic/ui
Change the appearance of the Gitea UI
labels
Mar 11, 2021
I see why you think so, but on the other hand I would expect, given that gitea is already able to display svg files as image, that they always offer the option to do so… |
see #14867 |
Duplicate of #14329 |
techknowlogick
added
issue/duplicate
The issue has already been reported.
and removed
type/feature
Completely new functionality. Can only be merged if feature freeze is not active.
topic/ui
Change the appearance of the Gitea UI
labels
Mar 17, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
Gitea supports showing SVGs as image and not as text, but apparently that only applies when viewing the file in the file view (example).
When opening a new PR, a SVG will still only be displayed as text in the preview and later on in the existing PR.
Expected behavior
Wherever in a repo a SVG image gets encountered, it should be displayed initially as image, not as text, but with the ability to convert it to raw text.
Screenshots
Appearance in file view:
Appearance in PR:
Appearance in PR preview:
The text was updated successfully, but these errors were encountered: