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
Display images inline in issues/pull requests #17419
Comments
I think it's a UX problem. If you paste the image from clipboard into the text area directly, it will be inserted automatically. But if you just drop files into the upload area or upload files manually, the file isn't inserted into the text area. |
Even when inserted from clipboard, there is a list of attached files. I don't that that is very useful and just clutters the UI. |
Agree, indeed, it is a UI/UX problem. |
It's better that the attached files could be collapsed. |
Duplicate of #12795? |
@lunny there is no need for an attached files list. it just clutters the UI. you wouldn't add it here. it does not fit example of files: @qwerty287 yes, i actually commented there. the title is a bit hard to find |
Feature Description
instead of the current image preview section
that way i can have the images in the context of my text that describe the issue seen in the image
the usage of images in issues and pull request does not really work currently, since the reader does not know which image you are referring to
example:
this is how it looks on gitea:
https://try.gitea.io/davidak/testing/issues/1
i selected both images to upload and they even have the wrong order, so the first line of text refers to the second image
another example:
same issue on gitea and github. in the latter, the images is bigger and is more helpful
https://git.gieszer.link/unfa/liblast/issues/92
godotengine/godot#53530
this is the biggest issue i have with gitea and it annoys me every time i add images to issues
please do it like github and gitlab does it!
(i thought there was an issue for this, but i was not able to find it)
Screenshots
No response
The text was updated successfully, but these errors were encountered: