Re: [w3c/manifest] Adding file_handlers and launch consumer (#1005)

@evanstade commented on this pull request.



> +          agent for privacy & security reasons.
+        </p>
+      </section>
+      <section data-cite="MIMETYPE">
+        <h3>
+          `accept` member
+        </h3>
+        <p>
+          The [=file handler=]'s <code><dfn data-dfn-for=
+          "file handler">accept</dfn></code> member is a <a>dictionary</a>
+          mapping [=MIME types=] to a list of [=file extensions=].
+        </p>
+        <p>
+          In order to [=register file handlers=], some operating systems
+          require [=MIME types=], some require [=file extensions=], and some
+          support both. Thus websites MUST always provide both for each [=file

Right, so, if an app used:

`  'image/jpeg': ['.txt']`

then it would work with .txt files on Windows and not work with anything on Linux.

> can the file extension be made to win on Linux

No, because Linux (`xdg-mime`) only associates mime types to apps. If we tried to use some custom MIME type, e.g. telling `xdg-mime` that this app supports `application/x-appid-type1` the problem would be that we couldn't convince `xdg-mime` to map `foo.txt` to this custom MIME type; it would still map it to `text/plain`.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/pull/1005#discussion_r787913142
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/pull/1005/review/857029518@github.com>