There is a problem with the implementation specs in 3.2.1 To process accept types ... which results in difficulties when using the current Chrome and Edge browsers.
There are cases where multiple extensions use the same MIME types, such as image/jpeg, text/plain, text/html. With the current spec it is not possible to ask for only one of the extensions, This is because the spec is basically an OR of the MIME type and the extensions.
'text/plain': ['.txt'] will ask the Chrome or Edge user for .txt AND .text.
Currently the only workaround is to use a meaningless MIME type, for example:
'foo/bar': ['.txt']
Several backward-compatible solutions may be possible:
An operator setting on the options that would specify whether accept is an OR or an AND of the MIME type and the extensions.
An extensions array of permitted extensions in the type. If present and the O/S supports extensions, it would override the accept.
A mimes array of permitted mime types in the type. If present and and extensions were not, it too would override the accept.
There is a problem with the implementation specs in 3.2.1 To process accept types ... which results in difficulties when using the current Chrome and Edge browsers.
There are cases where multiple extensions use the same MIME types, such as image/jpeg, text/plain, text/html. With the current spec it is not possible to ask for only one of the extensions, This is because the spec is basically an OR of the MIME type and the extensions.
'text/plain': ['.txt']will ask the Chrome or Edge user for .txt AND .text.Currently the only workaround is to use a meaningless MIME type, for example:
'foo/bar': ['.txt']Several backward-compatible solutions may be possible: