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

Content-type not shown correctly in file description #863

Closed
LavRadis opened this issue Dec 12, 2017 · 3 comments
Closed

Content-type not shown correctly in file description #863

LavRadis opened this issue Dec 12, 2017 · 3 comments
Assignees
Labels
area: viewer help wanted level: 2 Some knowledge of the existing code is recommended type: bug Existing functionality is wrong or broken

Comments

@LavRadis
Copy link
Contributor

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

  1. Open: lbry://3d-print-arrowhead-stl#936e8592f8ee5329a19a3afa203e051a220a6bce
  2. Check the file description

Expected behaviour

The content-type should be shown in accordance with real type

Actual behaviour

The description displayed is not correct

System Configuration

  • LBRY Daemon version: 0.18.0
  • LBRY App version: 0.19.0
  • LBRY Installation ID:
  • Operating system: Win 10

Screenshots

filetypeerror1
filetypeerror2

@tzarebczan
Copy link
Contributor

Thanks for opening this @LavRadis, sent you a tip on Discord!

@kauffj
Copy link
Member

kauffj commented Dec 12, 2017

This issue was moved to lbryio/lbry-sdk#1028

@kauffj kauffj closed this as completed Dec 12, 2017
@btzr-io btzr-io mentioned this issue Mar 14, 2018
@btzr-io 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
@btzr-io btzr-io mentioned this issue Mar 22, 2018
2 tasks
@btzr-io
Copy link
Collaborator

btzr-io commented Mar 22, 2018

Reopening issue, see possible solution: #1168

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
Projects
None yet
Development

No branches or pull requests

7 participants