This interface expands on the FileSaver interface to allow for multiple write actions, rather than just saving a single Blob.
The entire Blob has been written to the file, an error occurred during the write, or the write was aborted using abort(). The FileSaver is no longer writing the blob.
The blob is being written.
The object has been constructed, but there is no pending write.
The last error that occurred on the FileSaver.
The length of the file. If the user does not have read access to the file, this must be the highest byte offset at which the user has written.
Handler for abort events.
Handler for error events.
Handler for progress events.
Handler for write events.
Handler for writeend events.
Handler for writestart events
The byte offset at which the next write to the file will occur. This must be no greater than length. A newly-created FileWriter must have position set to 0.
The FileSaver object can be in one of 3 states. The readyState attribute, on getting, must return the current state, which must be one of the following values:
When the abort method is called, user agents must run the steps below:
boolean
Seek sets the file position at which the next write will occur.
If nonnegative, an absolute byte offset into the file. If negative, an offset back from the end of the file.
Changes the length of the file to that specified. If shortening the file, data beyond the new length must be discarded. If extending the file, the existing data must be zero-padded up to the new length.
The size to which the length of the file is to be adjusted, measured in bytes.
Write the supplied data to the file at position.
The blob to write.