but when going for the linux version i only get offered two options: open with an application (default here is VLC) or download but the "remember" button is grayed out.
for my impression the browser should be able to remember decisions for explicitly html/mime tagged file formats as already realized. but for for non-tagged or "wildcard"-tagged files and it shall be check for the file name extension (or absence of such an extension - this happens more often than you would think) and decide based upon that extension. so the browser needs not only a mime type default action configuration database/listing but an extension based handling if mime type is not that useable. maybe even the user can pass down certain mime types to the extension based treatment. thus the mime type layer should see a new option: "handle by file extension".
@Sergio - thats a nice proposal in that area. i can support that. its all about options.
BTW i think the dialog does not mention the mime type so i am a bit lost in diagnostics for that my faulty cases using purely the browser. the dialog should mention the mime-type he asks me about.
i am using Waterfox 24.0 (64 bit build version of firefox) on Windows 7 x86 64 bits.
when visiting this page: http:// software- dl.ti.com/ dsps/dsps_ public_ sw/sdo_ sb/targetconten t/tirtos/ 1_10_00_ 23/index_ FDS.html
(might require a free account to view or download)
and downloading the windows version (*.exe) of the file set
then i can select any option for opening or saving including the "remember my decision" option.
but when going for the linux version i only get offered two options: open with an application (default here is VLC) or download but the "remember" button is grayed out.
for my impression the browser should be able to remember decisions for explicitly html/mime tagged file formats as already realized. but for for non-tagged or "wildcard"-tagged files and it shall be check for the file name extension (or absence of such an extension - this happens more often than you would think) and decide based upon that extension. so the browser needs not only a mime type default action configuration database/listing but an extension based handling if mime type is not that useable. maybe even the user can pass down certain mime types to the extension based treatment. thus the mime type layer should see a new option: "handle by file extension".
@Sergio - thats a nice proposal in that area. i can support that. its all about options.
BTW i think the dialog does not mention the mime type so i am a bit lost in diagnostics for that my faulty cases using purely the browser. the dialog should mention the mime-type he asks me about.