You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
They will most likely contain the same list as the app/site is able to handle the same mime types/files, so does it really make sense that these are duplicated? @mgiuca
The text was updated successfully, but these errors were encountered:
The extension mapping discussed in w3c/web-share-target#74 could perhaps move to the top level of the manifest. Then only the list of MIME types would be listed twice. A web app might support only sharing or only file handing, so some repetition would be unavoidable.
That was my thought as well. For example: a text composition app (Word, Docs, etc.) might exist as a handler to open a particular file type, but also accept sharing of images, videos, etc. into the currently open document. Combining the lists would make drawing that distinction potentially challenging (especially if you support a bunch of file formats in varying scenarios).
They will most likely contain the same list as the app/site is able to handle the same mime types/files, so does it really make sense that these are duplicated? @mgiuca
The text was updated successfully, but these errors were encountered: