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

reconsider exporting mime types #656

Closed
matthiasclasen opened this issue Mar 23, 2017 · 2 comments

Comments

@matthiasclasen
Copy link
Collaborator

commented Mar 23, 2017

As we discussed at the hackfest, there are some issues with just allowing sandboxed applications to install new mimetypes or claim support for existing ones.

We need to carefully evaluate what we allow here, without exposing the user to risks.

One principle that was suggested is: Installing a new application should never change the default handler for an existing mime type.

@TingPing

This comment has been minimized.

Copy link
Member

commented Mar 23, 2017

One principle that was suggested is: Installing a new application should never change the default handler for an existing mime type.

I'm not sure that would really be possible across desktops as the desktop files are just thrown into the path and the machinery for looking up associations will just always find it? Some desktops still don't expose a UI for setting handlers either like Gnome..

@alexlarsson

This comment has been minimized.

Copy link
Member

commented May 19, 2017

We now rewrite and limit mimetypes as per: 3e9bc8b

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.