This document was published by the Web Applications Working Group as an Editors Draft. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at. Other documents may supersede this document. This section describes the status of this document at the time of its publication. These kinds of behaviors are defined in the appropriate affiliated specifications. with an overloaded send() method for File or Blob arguments), postMessage(), DataTransfer (part of the drag and drop API defined in )Īdditionally, it should be possible to programmatically obtain a list of files from the input element This API is designed to be used in conjunction with other APIs and elements on the web platform, notably: XMLHttpRequest (e.g. § 10 Requirements and Use Cases covers the motivation behind this specification. Ī URL scheme for use with binary data such as files, so that they can be referenced within web applications.Īdditionally, this specification defines objects to be used within threaded web applications for the synchronous reading of files.Ī FileReader interface, which provides methods to read a File or a Blob, and an event model to obtain the results of these reads.Ī File interface, which includes readonly informational attributes about a file such as its name and the date of the last modification (on disk) of the file.Ī Blob interface, which represents immutable raw binary data, and allows access to ranges of bytes within the Blob object as a separate Blob.when the input element is in the File Upload state. The user interface for selection can be invoked via, i.e.
This includes:Ī FileList interface, which represents an array of individually selected files from the underlying system. This specification provides an API for representing file objects in web applications,Īs well as programmatically selecting them and accessing their data.
0 kommentar(er)
