- From: <bugzilla@jessica.w3.org>
- Date: Thu, 23 Feb 2012 05:23:16 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=11482 --- Comment #25 from Michael[tm] Smith <mike@w3.org> 2012-02-23 05:23:12 UTC --- Comment 11 got lost somehow. No idea how, but I have asked the systems team to check on it. Here for the record is the original comment: --- Comment #11 from Sharon [MSFT] <sharco@microsoft.com> 2011-10-14 22:51:38 UTC --- In reply to comment #5 – I agree that there are some interesting use cases for image/*, video/* and audio/* strings. I’m not proposing removing those, however, we believe there are also good use cases for file extensions which are not covered by the existing options. Here is one specific example. A web developer who wants the user to upload a .csv file. The mime type for csv files is “application/vnd.ms-excel”. If you use this mime type in Chrome today you get only .xls file and in IE10 today you get .csv, .slk, .xla, .xld, .xlk, .xll, .xlm, .xls, .xlt and .xlw. Neither of these are really what the developer wanted. In reply to comment #9 – Section 12 of the spec already has some mentions of file extensions. Also the purpose of the accept attribute is to give the browser hints for how to request files from the OS. This seems like a logical place to use an OS concept even if it’s not known to the web platform. -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Thursday, 23 February 2012 05:23:18 UTC