Open dmoagx opened 8 years ago
I think we can close this c/o https://github.com/whatwg/html/issues/2861 being resolved?
The first use case for legacy backends can't be done until https://github.com/whatwg/html/issues/3269 is resolved somehow. We could use this as the File API side issue for that, as it'll need to change here eventually.
Split out from https://www.w3.org/Bugs/Public/show_bug.cgi?id=17125 :
The
element has always been readonly (you can't change value) for security purposes. That makes sense as a string could always be manipulated by JS.
The
File
object on the other hand should be "safe", as inSo it should not be a security issue to allow assignment to a file input. For example:
This code would split a multi-file-input back to multiple single-file inputs (that way applications with a legacy backend that only supports the classical way could also support multi-file-inputs).
Another use would be with File objects obtained by drag and drop. Right now those require XHR to upload. Allowing to make them a selection of a file input could simplify some situations as well as provide richer UI (when showing a traditional file input together with a drop area those would stay in sync).