Open Bug 1265602 Opened 8 years ago Updated 3 years ago

RFE: A mechanism to identify reason for 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
> Likewise, I'd be fine with us firing a special error from FileReader if the
> file changed on disk. But I don't think we currently do.

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.
But there is no way in the error handler to identify the reason for the failure.

Please provide a mechanism for JavaScript developer to identify failure reason so that s/he can take appropriate action.
See Also: → 1264371
See Also: → 1265603
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.

Bulk-downgrade of unassigned, >=3 years untouched DOM/Storage bug's priority.

If you have reason to believe this is wrong, 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.