File and Directory Entries API

Draft Community Group Report,

This version:
https://wicg.github.io/entries-api/
Test Suite:
https://github.com/web-platform-tests/wpt/tree/master/entries-api
Issue Tracking:
GitHub
Inline In Spec
Editor:
(Google Inc.)

Abstract

This specification documents web browser support for file and directory upload by drag-and-drop operations. It introduces types representing directories with methods for asynchronous traversal, and extends HTMLInputElement and DataTransferItem [HTML].

Status of this document

This specification was published by the Web Platform Incubator Community Group. It is not a W3C Standard nor is it on the W3C Standards Track. Please note that under the W3C Community Contributor License Agreement (CLA) there is a limited opt-out and other conditions apply. Learn more about W3C Community and Business Groups.

1. Goals

This specification documents the types and operations made available by web browsers to script when a hierarchy of files and directories are dragged and dropped onto a page or selected using form elements, or equivalent user actions.

This is heavily based upon earlier drafts of [file-system-api] which defines similar types in the context of a sandboxed file system, including operations for creating and modifying files and directories, but which has not been broadly adopted by web browsers.

note: The APIs described by this document was initially implemented in Google Chrome. Other browsers (at this time: Edge, Firefox and Safari) are starting to support subsets of Chrome’s APIs and behavior. The intent of this document is to specify the common subset to ensure that the implementations are interoperable.

2. Concepts

2.1. Names and Paths

A name is a string which:

A path segment is a name, '.' (U+002E FULL STOP) or '..' (U+002E FULL STOP, U+002E FULL STOP).

A relative path is a string consisting of one or more path segments joined by '/' (U+002F SOLIDUS) that does not start with '/' (U+002F SOLIDUS).

An absolute path is a string consisting of '/' (U+002F SOLIDUS) followed by zero or more path segments joined by '/' (U+002F SOLIDUS).

A path is either a relative path or an absolute path.

A valid path is a USVString which is a path.

2.2. Files and Directories

A file consists of binary data and a name (a non-empty name).

A directory consists of a name (a name) and an ordered list of members. Each member is either a file or a directory. Each member of a directory must have a distinct non-empty name.

A root directory is a directory that is not a member of a directory. A root directory's name is empty.

The parent of a file or directory is the directory it is a member of. A root directory has no parent.

EDITORIAL: Should directory be defined as a special type of file so that minimal changes are necessary in [HTML]?

note: In most cases, the files and directories selected by the user will be presented by the API as if contained by a virtual root that does not exist as an entity in the actual native file system backing the interaction with the API.

A file system consists of a name and a root which is an associated root directory. The name of a file system is a USVString which is implementation defined but is unique to the file system. A root directory is associated with exactly one file system.

note: Implementations could produce a name by generating a UUID for each file system instance with some fixed prefix and suffix strings applied. Authors using the API are adviised not to make assumptions about the structure or content of the names.

2.3. Entries

An entry is either a file entry or a directory entry.

An entry has an name (a name) and a full path (an absolute path).

An entry also has a root, which is an associated root directory.

note: Entries are defined in terms of paths relative to a root directory to account for the fact that a native file system backing the interaction with the API could be modified asynchronously during operations such as enumerating the contents of a directory. Operations exposed on entries will produce errors in such cases where the paths no longer reference the same entity.

The file system of an entry is the file system associated with the entry's root.

3. Algorithms

To resolve a relative path with abspath (an absolute path) and path (an absolute path, a relative path, or the empty string), perform the following steps. They return an absolute path.

  1. If path is an absolute path, return path.

  2. Let abspath segments be the result of strictly splitting abspath on '/' (U+002F SOLIDUS).

    note: The first string will be empty.

  3. Let path segments be the result of strictly splitting path on '/' (U+002F SOLIDUS).

  4. For each segment in path segments, switch on segment:

    empty string

    Continue.

    '.' (U+002E FULL STOP)

    Continue.

    '..' (U+002E FULL STOP, U+002E FULL STOP)

    Remove the last member of abspath segments unless it is the only member.

    Otherwise

    Append segment to abspath segments.

  5. Return abspath segments joined by '/' (U+002F SOLIDUS).

To evaluate a path with directory (an root directory) and path (an absolute path), perform the following steps. They return a file, directory, or failure.

  1. Let segments be the result of strictly splitting path on '/' (U+002F SOLIDUS).

  2. Remove the first entry from segments.

    note: Since path was an absolute path, this first entry will always be empty.

  3. For each segment in segments, switch on segment:

    empty string

    Continue.

    '.' (U+002E FULL STOP)

    Continue.

    '..' (U+002E FULL STOP, U+002E FULL STOP)

    Let directory be directory’s parent, or directory if none.

    Otherwise

    Run these steps:

    1. Let item be the member of directory with name equal to segment, or return failure if none.

    2. If segment is the last item in segments, return item.

    3. If item is a file, return failure.

    4. Let directory be item.

4. The File Interface

EDITORIAL: This section should be merged into [FileAPI] once it is complete.
partial interface File {
    readonly attribute USVString webkitRelativePath;
};

The webkitRelativePath getter steps are to return this's relative path, or the empty string if not specified.

5. HTML: Forms

EDITORIAL: This section should be merged into [HTML] once it is complete. Sections such as the steps to construct the entry list need to be extended to include the webkitRelativePath property.
partial interface HTMLInputElement {
    attribute boolean webkitdirectory;
    readonly attribute FrozenArray<FileSystemEntry> webkitEntries;
};

When an input element’s type attribute is in the File Upload state, the rules in this section apply.

The webkitdirectory attribute is a boolean attribute that indicates whether the user is to be allowed to select a directory rather than a file or files. When specified, the behavior on the selection of a directory is as if all files with that directory as an ancestor were selected. In addition, the webkitRelativePath property of each File is set to a relative path starting from (and including) the selected directory to the file.

Given the following directory structure:
documents/
  to_upload/
    a/
      b/
        1.txt
        2.txt
      3.txt
  not_uploaded.txt

If the to_upload directory was selected, then files would include:

note: A user agent could represent any hierarchical data as directories during a selection operation. For example, on a device that does not expose a native file system directly to the user, photo albums could be presented as directories if "image/*" is specified for the accept attribute.

Inspecting the webkitRelativePath properties after a directory is selected with an input element:
<input id=b type=file webkitdirectory>
document.querySelector('#b').addEventListener('change', e => {
  for (file entry of e.target.files) {
    console.log(file.name, file.webkitRelativePath);
  }
});

The webkitEntries IDL attribute allows scripts to access the element’s selected entries. On getting, if the IDL attribute applies, it must return an array of FileSystemEntry objects that represent the current selected files (including directories, if permitted). If the IDL attribute does not apply, then it must instead return null.

Enumerating entries using webkitEntries:
<input id=a type=file multiple>
document.querySelector('#a').addEventListener('change', e => {
  for (const entry of e.target.webkitEntries) {
    handleEntry(entry);
  }
});
INTEROP: In Chrome, webkitEntries is only populated as the result of a drag-and-drop operation, not when the element is clicked. Should we fix this so it is always populated?
INTEROP: In Chrome, if webkitdirectory is specified on a HTMLInputElement, webkitEntries is not populated; the files collection and webkitRelativePath properties must be used instead to reconstruct the directory structure. Should we fix this so it is always populated?

6. HTML: Drag and drop

EDITORIAL: This section should be merged into [HTML] once it is complete.

During a drag-and-drop operation, file and directory items are associated with entries. Each entry is a member of a root directory unique to the drag data store.

Additionally, each directory item is represented in the drag data store item list as an item whose kind is File. If it is accessed via getAsFile() a zero-length File is returned.

note: A user agent could represent any hierarchical data as files and directories during a drag-and-drop operation. For example, audio data stored in a relational database with separate tables for albums metadata and blobs for tracks could be exposed to script as directories and files when dragged from a media player application.

partial interface DataTransferItem {
    FileSystemEntry? webkitGetAsEntry();
};

The webkitGetAsEntry() method steps are:

  1. Let store be this's DataTransfer object’s drag data store.

  2. If store’s drag data store mode is not read/write mode or read-only mode, return null and abort these steps.

  3. Let item be the item in store’s drag data store item list that this represents.

  4. If item’s kind is not File, then return null and abort these steps.

  5. Return a new FileSystemEntry object representing the entry.

Handling drag and drop of files and directories:
elem.addEventListener('dragover', e => {
  // Prevent navigation.
  e.preventDefault();
});
elem.addEventListener('drop', e => {
  // Prevent navigation.
  e.preventDefault();

  // Process all of the items.
  for (const item of e.dataTransfer.items) {
    // kind will be 'file' for file/directory entries.
    if (item.kind === 'file') {
      const entry = item.webkitGetAsEntry();
      handleEntry(entry);
    }
  }
});

7. Files and Directories

WEB COMPAT: The legacy TypeMismatchError has been replaced in most specifications by TypeError, but the name differs. Is it compatible to switch here as well?
callback ErrorCallback = undefined (DOMException err);

An ErrorCallback function is used for operations that may return an error asynchronously.

The task source used for tasks that are queued in steps below is not defined. Chromium-based browsers appear to use the following:

7.1. The FileSystemEntry Interface

[Exposed=Window]
interface FileSystemEntry {
    readonly attribute boolean isFile;
    readonly attribute boolean isDirectory;
    readonly attribute USVString name;
    readonly attribute USVString fullPath;
    readonly attribute FileSystem filesystem;

    undefined getParent(optional FileSystemEntryCallback successCallback,
                   optional ErrorCallback errorCallback);
};

An FileSystemEntry has an associated entry.

The isFile getter steps are to return true if this is a file entry and false otherwise.

The isDirectory getter steps are to return true if this is a directory entry and false otherwise.

The name getter steps are to return this's name.

The fullPath getter steps are to return this's full path.

The filesystem getter steps are to return this's file system.

The getParent(successCallback, errorCallback) method steps are:

  1. In parallel, run these steps:

    1. Let path be the result of resolving a relative path with this's full path and '..'.

    2. Let item be the result of evaluating a path with this's root and path.

    3. If item is failure, queue a task to invoke errorCallback (if given) with a newly created "NotFoundError" DOMException, and abort these steps.

    4. Let entry be a new directory entry with item’s name as name and path as full path.

    5. Queue a task to invoke successCallback with a new FileSystemDirectoryEntry object associated with entry.

note: An error is possible if files have been modified on disk since the FileSystemEntry was created.

Handling an entry:
function handleEntry(entry) {
  console.log('name: ' + entry.name);
  console.log('path: ' + entry.fullPath);
  if (entry.isFile) {
    console.log('... is a file');
  } else if (entry.isDirectory) {
    console.log('... is a directory');
  }
}
Helper function to adapt getParent() for use with Promises [ECMA-262]:
function getParentAsPromise(entry) {
  return new Promise((resolve, reject) => {
    entry.getParent(resolve, reject);
  });
}

7.2. The FileSystemDirectoryEntry Interface

[Exposed=Window]
interface FileSystemDirectoryEntry : FileSystemEntry {
    FileSystemDirectoryReader createReader();
    undefined getFile(optional USVString? path,
                 optional FileSystemFlags options = {},
                 optional FileSystemEntryCallback successCallback,
                 optional ErrorCallback errorCallback);
    undefined getDirectory(optional USVString? path,
                      optional FileSystemFlags options = {},
                      optional FileSystemEntryCallback successCallback,
                      optional ErrorCallback errorCallback);
};

dictionary FileSystemFlags {
    boolean create = false;
    boolean exclusive = false;
};

callback FileSystemEntryCallback = undefined (FileSystemEntry entry);

note: The create member of FileSystemFlags and the associated behavior are included for compatibility with existing implementations, even though there is no useful behavior when the flag is specified. Similarly, the exclusive member is not explicitly referenced, but the binding behavior is observable from script if an object with a getter is passed.

A FileSystemDirectoryEntry's associated entry is a directory entry.

The createReader() method steps are:

  1. Return a newly created FileSystemDirectoryReader object associated with directory entry.

The getFile(path, options, successCallback, errorCallback) method steps are:

  1. In parallel, run these steps:

    1. If path is undefined or null let path be the empty string.

    2. If path is not a valid path, queue a task to invoke errorCallback (if given) with a newly created "TypeMismatchError" DOMException, and abort these steps.

    3. If options’s create member is true, queue a task to invoke errorCallback (if given) with a newly created "SecurityError" DOMException, and abort these steps.

    4. Let path be the result of resolving a relative path with this's full path and path.

    5. Let item be the result of evaluating a path with this's root and path.

    6. If item is failure, queue a task to invoke errorCallback (if given) with a newly created "NotFoundError" DOMException, and abort these steps.

    7. If item is not a file, queue a task to invoke errorCallback (if given) with a newly created "TypeMismatchError" DOMException, and abort these steps.

    8. Let entry be a new file entry with item’s name as name and path as full path.

    9. Queue a task to invoke successCallback (if given) with a new FileSystemFileEntry object associated with entry.

The getDirectory(path, options, successCallback, errorCallback) method steps are:

  1. In parallel, run these steps:

    1. If path is undefined or null let path be the empty string.

    2. If path is not a valid path, queue a task to invoke errorCallback (if given) with a newly created "TypeMismatchError" DOMException, and abort these steps.

    3. If options’s create member is true, queue a task to invoke errorCallback (if given) with a newly created "SecurityError" DOMException, and abort these steps.

    4. Let path be the result of resolving a relative path with this's full path and path.

    5. Let item be the result of evaluating a path with this's root and path.

    6. If item is failure, queue a task to invoke errorCallback (if given) with a newly created "NotFoundError" DOMException, and abort these steps.

    7. If item is not a directory, invoke errorCallback (if given) with a newly created "TypeMismatchError" DOMException, and abort these steps.

    8. Let entry be a new directory entry with item’s name as name and path as full path.

    9. Queue a task to invoke successCallback (if given) with a new FileSystemDirectoryEntry associated with entry.

Helper functions to adapt getFile() and getDirectory() for use with Promises [ECMA-262]:
function getFileAsPromise(entry, path) {
  return new Promise((resolve, reject) => {
    entry.getFile(path, {}, resolve, reject);
  });
}
function getDirectoryAsPromise(entry, path) {
  return new Promise((resolve, reject) => {
    entry.getDirectory(path, {}, resolve, reject);
  });
}

7.3. The FileSystemDirectoryReader Interface

[Exposed=Window]
interface FileSystemDirectoryReader {
    undefined readEntries(FileSystemEntriesCallback successCallback,
                     optional ErrorCallback errorCallback);
};
callback FileSystemEntriesCallback = undefined (sequence<FileSystemEntry> entries);
A FileSystemDirectoryReader has an associated entry (a directory entry), an associated directory (initially null), a reading flag (initially false), a done flag (initially false), and a reader error (initially null).

The readEntries(successCallback, errorCallback) method steps are:

  1. If this's reading flag is true, queue a task to invoke errorCallback with a newly created "InvalidStateError" DOMException, and abort these steps.

  2. If this's reader error is not null, queue a task to invoke errorCallback (if given) with reader error, and abort these steps.

  3. If this's done flag is true, queue a task to invoke successCallback with an empty sequence and abort these steps.

  4. Set this's reading flag to true.

  5. In parallel, run these steps:

    1. If this's directory is null, then:

      1. Let dir be the result of evaluating a path with this's entry's root and full path.

      2. If dir is failure, then:

        1. Queue a task to run these steps:

          1. Let error be a newly created "NotFoundError" DOMException.

          2. Set this's reader error to error.

          3. Set this's reading flag to false.

          4. Invoke errorCallback (if given) with error.

        2. Abort these steps.

      3. Set this's directory to dir.

    2. Let entries be a non-zero number of entries from this's directory that have not yet been produced by this FileSystemDirectoryReader, if any.

    3. If the previous step failed (for example, the directory was deleted or permission is denied), then:

      1. Queue a task to run these steps:

        1. Let error be a an appropriate DOMException.

        2. Set this's reader error to error.

        3. Set this's reading flag to false.

        4. Invoke errorCallback (if given) with reader error.

      2. Abort these steps.

    4. Queue a task to run these steps:

      1. If entries is empty, then set this's done flag to true.

      2. Set this's reading flag to false.

      3. Invoke successCallback with entries.

NOTE: The use of the the reading flag prevents multiple copies of the in parallel steps above from executing simultaneously. This obviates the need to specify a parallel queue.

Enumerating a directory:
const reader = dirEntry.createReader();
const doBatch = () => {

  // Read a batch.
  reader.readEntries(entries => {

    // Complete?
    if (entries.length === 0) {
      return;
    }

    // Process the batch.
    entries.forEach(handleEntry);

    // Read the next batch.
    doBatch();

  }, error => console.warn(error));
};

// Start reading
doBatch();
Helper function to adapt FileSystemDirectoryReader for use with Promises [ECMA-262]:
function getEntriesAsPromise(dirEntry) {
  return new Promise((resolve, reject) => {
    const result = [];
    const reader = dirEntry.createReader();
    const doBatch = () => {
      reader.readEntries(entries => {
        if (entries.length > 0) {
          entries.forEach(e => result.push(e));
          doBatch();
        } else {
          resolve(result);
        }
      }, reject);
    };
    doBatch();
  });
}
Helper function to adapt FileSystemDirectoryReader for use with AsyncIterators [ECMA-262]:
async function* getEntriesAsAsyncIterator(dirEntry) {
  const reader = dirEntry.createReader();
  const getNextBatch = () => new Promise((resolve, reject) => {
    reader.readEntries(resolve, reject);
  });

  let entries;
  do {
    entries = await getNextBatch();
    for (const entry of entries) {
      yield entry;
    }
  } while (entries.length > 0);
}

This allows for ordered asynchronous traversal of a directory tree using for-await-of:

async function show(entry) {
  console.log(entry.fullPath);
  if (entry.isDirectory) {
    for await (const e of getEntriesAsAsyncIterator(entry)) {
      await show(e);
    }
  }
}

7.4. The FileSystemFileEntry Interface

[Exposed=Window]
interface FileSystemFileEntry : FileSystemEntry {
    undefined file(FileCallback successCallback,
              optional ErrorCallback errorCallback);
};
callback FileCallback = undefined (File file);

A FileSystemFileEntry's associated entry is a file entry.

The file(successCallback, errorCallback) method steps are:

  1. In parallel, run these steps:

    1. Let item be the result of evaluating a path with this's root and full path.

    2. If item is failure, queue a task to invoke errorCallback (if given) with a newly created "NotFoundError" DOMException, and abort these steps.

    3. If item is a directory, queue a task to invoke errorCallback (if given) with a newly created "TypeMismatchError" DOMException, and abort these steps.

    4. Queue a task to invoke successCallback with a new File object representing item.

Read the contents of a dropped file using FileReader:
function readFileEntry(entry) {
  entry.file(file => {
    const reader = new FileReader();
    reader.readAsText(file);
    reader.onerror = error => console.warn(error);
    reader.onload = () => {
      console.log(reader.result);
    };
  }, error => console.warn(error));
}
Helper function to adapt file() for use with Promises [ECMA-262]:
function fileAsPromise(entry) {
  return new Promise((resolve, reject) => {
    entry.file(resolve, reject);
  });
}

7.5. The FileSystem Interface

[Exposed=Window]
interface FileSystem {
    readonly attribute USVString name;
    readonly attribute FileSystemDirectoryEntry root;
};

A FileSystem has an associated file system.

The name getter steps are to return this's name.

The root getter steps are to return a FileSystemDirectoryEntry associated with this's root.

8. Acknowledgements

This specification is based heavily on the work of Eric Uhrhane in [file-system-api], which introduced the FileSystemEntry types.

Thanks to Tab Atkins, Jr. for creating and maintaining Bikeshed, the specification authoring tool used to create this document.

And thanks to Ali Alabbas, Philip Jägenstedt, Marijn Kruisselbrink, Olli Pettay, and Kent Tamura for suggestions, reviews, and other feedback.

Conformance

Document conventions

Conformance requirements are expressed with a combination of descriptive assertions and RFC 2119 terminology. The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this document are to be interpreted as described in RFC 2119. However, for readability, these words do not appear in all uppercase letters in this specification.

All of the text of this specification is normative except sections explicitly marked as non-normative, examples, and notes. [RFC2119]

Examples in this specification are introduced with the words “for example” or are set apart from the normative text with class="example", like this:

This is an example of an informative example.

Informative notes begin with the word “Note” and are set apart from the normative text with class="note", like this:

Note, this is an informative note.

Index

Terms defined by this specification

Terms defined by reference

References

Normative References

[FileAPI]
Marijn Kruisselbrink. File API. URL: https://w3c.github.io/FileAPI/
[HTML]
Anne van Kesteren; et al. HTML Standard. Living Standard. URL: https://html.spec.whatwg.org/multipage/
[INFRA]
Anne van Kesteren; Domenic Denicola. Infra Standard. Living Standard. URL: https://infra.spec.whatwg.org/
[RFC2119]
S. Bradner. Key words for use in RFCs to Indicate Requirement Levels. March 1997. Best Current Practice. URL: https://datatracker.ietf.org/doc/html/rfc2119
[WEBIDL]
Edgar Chen; Timothy Gu. Web IDL Standard. Living Standard. URL: https://webidl.spec.whatwg.org/

Informative References

[ECMA-262]
ECMAScript Language Specification. URL: https://tc39.es/ecma262/multipage/
[FILE-SYSTEM-API]
Eric Uhrhane. File API: Directories and System. URL: https://dev.w3.org/2009/dap/file-system/file-dir-sys.html

IDL Index

partial interface File {
    readonly attribute USVString webkitRelativePath;
};

partial interface HTMLInputElement {
    attribute boolean webkitdirectory;
    readonly attribute FrozenArray<FileSystemEntry> webkitEntries;
};

partial interface DataTransferItem {
    FileSystemEntry? webkitGetAsEntry();
};

callback ErrorCallback = undefined (DOMException err);

[Exposed=Window]
interface FileSystemEntry {
    readonly attribute boolean isFile;
    readonly attribute boolean isDirectory;
    readonly attribute USVString name;
    readonly attribute USVString fullPath;
    readonly attribute FileSystem filesystem;

    undefined getParent(optional FileSystemEntryCallback successCallback,
                   optional ErrorCallback errorCallback);
};

[Exposed=Window]
interface FileSystemDirectoryEntry : FileSystemEntry {
    FileSystemDirectoryReader createReader();
    undefined getFile(optional USVString? path,
                 optional FileSystemFlags options = {},
                 optional FileSystemEntryCallback successCallback,
                 optional ErrorCallback errorCallback);
    undefined getDirectory(optional USVString? path,
                      optional FileSystemFlags options = {},
                      optional FileSystemEntryCallback successCallback,
                      optional ErrorCallback errorCallback);
};

dictionary FileSystemFlags {
    boolean create = false;
    boolean exclusive = false;
};

callback FileSystemEntryCallback = undefined (FileSystemEntry entry);

[Exposed=Window]
interface FileSystemDirectoryReader {
    undefined readEntries(FileSystemEntriesCallback successCallback,
                     optional ErrorCallback errorCallback);
};
callback FileSystemEntriesCallback = undefined (sequence<FileSystemEntry> entries);

[Exposed=Window]
interface FileSystemFileEntry : FileSystemEntry {
    undefined file(FileCallback successCallback,
              optional ErrorCallback errorCallback);
};
callback FileCallback = undefined (File file);

[Exposed=Window]
interface FileSystem {
    readonly attribute USVString name;
    readonly attribute FileSystemDirectoryEntry root;
};

Issues Index

EDITORIAL: Should directory be defined as a special type of file so that minimal changes are necessary in [HTML]?
EDITORIAL: This section should be merged into [FileAPI] once it is complete.
EDITORIAL: This section should be merged into [HTML] once it is complete. Sections such as the steps to construct the entry list need to be extended to include the webkitRelativePath property.
INTEROP: In Chrome, webkitEntries is only populated as the result of a drag-and-drop operation, not when the element is clicked. Should we fix this so it is always populated?
INTEROP: In Chrome, if webkitdirectory is specified on a HTMLInputElement, webkitEntries is not populated; the files collection and webkitRelativePath properties must be used instead to reconstruct the directory structure. Should we fix this so it is always populated?
EDITORIAL: This section should be merged into [HTML] once it is complete.
WEB COMPAT: The legacy TypeMismatchError has been replaced in most specifications by TypeError, but the name differs. Is it compatible to switch here as well?
The task source used for tasks that are queued in steps below is not defined. Chromium-based browsers appear to use the following:
MDN

DataTransferItem/webkitGetAsEntry

In all current engines.

Firefox50+Safari11.1+Chrome13+
Opera?Edge79+
Edge (Legacy)14+IENone
Firefox for AndroidNoneiOS Safari?Chrome for Android?Android WebView?Samsung Internet?Opera Mobile?
MDN

File/webkitRelativePath

In all current engines.

Firefox50+Safari11.1+Chrome13+
Opera?Edge79+
Edge (Legacy)13+IENone
Firefox for Android?iOS Safari?Chrome for Android?Android WebView37+Samsung Internet?Opera Mobile?
MDN

FileSystem/name

In all current engines.

Firefox50+Safari11.1+Chrome7+
Opera?Edge79+
Edge (Legacy)18IENone
Firefox for Android?iOS Safari?Chrome for Android?Android WebView37+Samsung Internet?Opera Mobile?
MDN

FileSystem/root

In all current engines.

Firefox50+Safari11.1+Chrome7+
Opera?Edge79+
Edge (Legacy)18IENone
Firefox for Android?iOS Safari?Chrome for Android?Android WebView37+Samsung Internet?Opera Mobile?
MDN

FileSystem

In all current engines.

Firefox50+Safari11.1+Chrome7+
Opera?Edge79+
Edge (Legacy)18IENone
Firefox for Android?iOS Safari?Chrome for Android?Android WebView37+Samsung Internet?Opera Mobile?
MDN

FileSystemDirectoryEntry/createReader

In all current engines.

Firefox50+Safari11.1+Chrome13+
OperaNoneEdge79+
Edge (Legacy)?IENone
Firefox for Android?iOS Safari?Chrome for Android?Android WebView37+Samsung Internet?Opera Mobile?
MDN

FileSystemDirectoryEntry/getDirectory

In all current engines.

Firefox50+Safari11.1+Chrome8+
OperaNoneEdge79+
Edge (Legacy)?IENone
Firefox for Android?iOS Safari?Chrome for Android?Android WebView37+Samsung Internet?Opera Mobile?
MDN

FileSystemDirectoryEntry/getFile

In all current engines.

Firefox50+Safari11.1+Chrome8+
OperaNoneEdge79+
Edge (Legacy)?IENone
Firefox for Android?iOS Safari?Chrome for Android?Android WebView37+Samsung Internet?Opera Mobile?
MDN

FileSystemDirectoryEntry

In all current engines.

Firefox50+Safari11.1+Chrome8+
Opera?Edge79+
Edge (Legacy)?IENone
Firefox for Android?iOS Safari?Chrome for Android?Android WebView37+Samsung Internet?Opera Mobile?
MDN

FileSystemDirectoryReader/readEntries

In all current engines.

Firefox50+Safari11.1+Chrome8+
Opera?Edge79+
Edge (Legacy)?IENone
Firefox for Android?iOS Safari?Chrome for Android?Android WebView37+Samsung Internet?Opera Mobile?
MDN

FileSystemDirectoryReader

In all current engines.

Firefox50+Safari11.1+Chrome8+
Opera?Edge79+
Edge (Legacy)18IENone
Firefox for Android?iOS Safari?Chrome for Android?Android WebView37+Samsung Internet?Opera Mobile?
MDN

FileSystemEntry/filesystem

In all current engines.

Firefox50+Safari11.1+Chrome8+
OperaNoneEdge79+
Edge (Legacy)?IENone
Firefox for Android?iOS Safari?Chrome for Android?Android WebView37+Samsung Internet?Opera Mobile?
MDN

FileSystemEntry/fullPath

In all current engines.

Firefox50+Safari11.1+Chrome8+
OperaNoneEdge79+
Edge (Legacy)?IENone
Firefox for Android?iOS Safari?Chrome for Android?Android WebView37+Samsung Internet?Opera Mobile?
MDN

FileSystemEntry/getParent

In all current engines.

Firefox52+Safari11.1+Chrome8+
OperaNoneEdge79+
Edge (Legacy)?IENone
Firefox for Android?iOS Safari?Chrome for Android?Android WebView37+Samsung Internet?Opera Mobile?
MDN

FileSystemEntry/isDirectory

In all current engines.

Firefox50+Safari11.1+Chrome8+
OperaNoneEdge79+
Edge (Legacy)?IENone
Firefox for Android?iOS Safari?Chrome for Android?Android WebView37+Samsung Internet?Opera Mobile?
MDN

FileSystemEntry/isFile

In all current engines.

Firefox50+Safari11.1+Chrome8+
OperaNoneEdge79+
Edge (Legacy)?IENone
Firefox for Android?iOS Safari?Chrome for Android?Android WebView37+Samsung Internet?Opera Mobile?
MDN

FileSystemEntry/name

In all current engines.

Firefox50+Safari11.1+Chrome8+
OperaNoneEdge79+
Edge (Legacy)?IENone
Firefox for Android?iOS Safari?Chrome for Android?Android WebView37+Samsung Internet?Opera Mobile?
MDN

FileSystemEntry

In all current engines.

Firefox50+Safari11.1+Chrome8+
OperaNoneEdge79+
Edge (Legacy)?IENone
Firefox for Android?iOS Safari?Chrome for Android?Android WebView37+Samsung Internet?Opera Mobile?
MDN

FileSystemFileEntry/file

In all current engines.

Firefox50+Safari11.1+Chrome8+
OperaNoneEdge79+
Edge (Legacy)?IENone
Firefox for Android?iOS Safari?Chrome for Android?Android WebView37+Samsung Internet?Opera Mobile?
MDN

FileSystemFileEntry

In all current engines.

Firefox50+Safari11.1+Chrome8+
OperaNoneEdge79+
Edge (Legacy)?IENone
Firefox for Android?iOS Safari?Chrome for Android?Android WebView37+Samsung Internet?Opera Mobile?
MDN

HTMLInputElement/webkitdirectory

In all current engines.

Firefox50+Safari11.1+Chrome7+
Opera?Edge79+
Edge (Legacy)13+IENone
Firefox for AndroidNoneiOS Safari?Chrome for Android?Android WebView?Samsung Internet?Opera Mobile?
MDN

HTMLInputElement/webkitEntries

In all current engines.

Firefox50+Safari11.1+Chrome22+
Opera?Edge79+
Edge (Legacy)?IENone
Firefox for AndroidNoneiOS Safari?Chrome for Android?Android WebViewNoneSamsung Internet?Opera Mobile?