Open Bug 1265603 Opened 8 years ago Updated 3 years ago

RFE: A mechanism to recover from failure of FileReader.readAsText(HTML_FORM_INPUT.files[0]) after file got modified.


(Core :: DOM: Core & HTML, enhancement, P5)




Tracking Status
firefox48 --- affected


(Reporter: BijuMailList, Unassigned)



See Bug 1260606 comment #28
> I think we could return a different File object from
> HTMLInputElement.files[0] if the file changed on disk.

If a file was modified after it was selected using INPUT[type=file], from Firefox 45 build FileReader.readAsText(HTML_FORM_INPUT.files[0]) fails.
JavaScript developer need a mechanism to recover from such a failure.
See Also: → 1264371
My proposal here is that when a file changes, that we make inputElement.files[0] return a new File object which is updated to contain the new metadata.
So, basically when the FileReader fails, we have to go back to the HTMLInputElement.files and try again.
The only strange thing is that .files attribute changes value without having any event to inform about it.
If by "we" you mean the web developer, then yes, that's my proposal.
I want add one more situation, there will also case where file was deleted from the disk or there is network fault (if file was network, or on removable disk) after user selected it with FORM_INPUT file control.
See Also: → 1265602

Bulk-downgrade of unassigned, 4 years untouched DOM/Storage bugs' priority.

If you have reason to believe this is wrong (especially for the severity), please write a comment and ni :jstutte.

Severity: normal → S4
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.