This feature is no longer recommended. Though some browsers might still support it, it may have already been removed from the relevant web standards, may be in the process of being dropped, or may only be kept for compatibility purposes. Avoid using it, and update existing code if possible; see the compatibility table at the bottom of this page to guide your decision. Be aware that this feature may cease to work at any time.
Note: This method is deprecated in favor of
readAsBinaryString()method of the
FileReaderSyncinterface allows to read
Blobobjects in a synchronous way into an
DOMString. This interface is only available in workers as it enables synchronous I/O that could potentially block.
DOMString representing the input data.
The following exceptions can be raised by this method:
- is raised when the resource represented by the DOM
Blobcannot be found, e.g. because it has been erased.
- is raised when one of the following problematic situation is detected:
- the resource has been modified by a third party;
- too many read are performed simultaneously;
- the file pointed by the resource is unsafe for a use from the Web (like it is a system file).
- is raised when the resource cannot be read due to a permission problem, like a concurrent lock.
- is raised when the resource is a data URL and exceed the limit length defined by each browser.
The definition of 'readAsBinaryStringSync' in that specification.
|Working Draft||Initial definition.|
|Chrome Full support Yes||Edge Full support Yes||Firefox Full support 8||IE Full support Yes||Opera Full support Yes||Safari Full support Yes||WebView Android Full support Yes||Chrome Android Full support Yes||Firefox Android Full support 8||Opera Android Full support Yes||Safari iOS Full support Yes||Samsung Internet Android Full support Yes|
- Full support
- Full support