-
Notifications
You must be signed in to change notification settings - Fork 414
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
Content-type not shown correctly in file description #863
Labels
area: viewer
help wanted
level: 2
Some knowledge of the existing code is recommended
type: bug
Existing functionality is wrong or broken
Comments
Thanks for opening this @LavRadis, sent you a tip on Discord! |
This issue was moved to lbryio/lbry-sdk#1028 |
Closed
btzr-io
added
type: bug
Existing functionality is wrong or broken
type: improvement
Existing (or partially existing) functionality needs to be changed
labels
Mar 22, 2018
Reopening issue, see possible solution: #1168 |
Merged
liamcardenas
added
help wanted
level: 2
Some knowledge of the existing code is recommended
area: viewer
and removed
needs: triage
type: improvement
Existing (or partially existing) functionality needs to be changed
labels
Apr 18, 2018
Ruk33
pushed a commit
that referenced
this issue
Feb 25, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area: viewer
help wanted
level: 2
Some knowledge of the existing code is recommended
type: bug
Existing functionality is wrong or broken
The Issue
For some file types, the "Content-Type" description is not shown correctly. I've noticed that for .odt (open office files) and .stl (3d printing files) the description is "application". It could be confusing for users and discourage downloads.
Some other users have also mentioned the issue in Discord.
Steps to reproduce
Expected behaviour
The content-type should be shown in accordance with real type
Actual behaviour
The description displayed is not correct
System Configuration
Screenshots
The text was updated successfully, but these errors were encountered: