You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<p>This section defines and explains terms used in the File and Directory Entries API.</p>
187
187
188
188
<dl>
189
-
<dt><aname="gloss_blob">blob</a></dt>
189
+
<dt>blob</dt>
190
190
<dd>Stands for binary large object. A blob is a set of binary data that is stored as a single object. It is a general-purpose way to reference binary data in web applications. A blob can be an image or an audio file.</dd>
191
-
<dt><aname="gloss_Blob">Blob</a></dt>
191
+
<dt>Blob</dt>
192
192
<dd>Blob—with a capital B—is a data structure that is immutable, which means that binary data referenced by a Blob cannot be modified directly. This makes Blobs act predictably when they are passed to asynchronous APIs.</dd>
<dd>Transient storage is available to any web app. It is automatic and does not need to be requested, but the browser can delete the storage without warning.</dd>
<td>The modification requested is not allowed. Examples of invalid modifications include moving a directory into its own child or moving a file into its parent directory without changing its name.</td>
<td>The operation cannot be performed on the current state of the interface object. For example, the state that was cached in an interface object has changed since it was last read from disk.</td>
<td>A required file or directory could not be found at the time an operation was processed. For example, a file did not exist but was being opened.</td>
<p>The file or directory cannot be read, typically due to permission problems that occur after a reference to a file has been acquired (for example, the file or directory is concurrently locked by another application).</p>
<td>The user has attempted to look up a file or directory, but the Entry found is of the wrong type. For example, the app is accessing a DirectoryEntry when the user is requesting a FileEntry.</td>
<td>A mutation operation in the transaction failed because a constraint was not satisfied. For example, an object, such as an object store or index, already exists and a request attempted to create a new one.</td>
<p>An operation was called on an object where it is not allowed or at a time when it is not allowed. It also occurs if a request is made on a source object that has been deleted or removed.</p>
<td>The operation failed because the requested database object could not be found; for example, an object store did not exist but was being opened.</td>
<td>The operation failed for reasons unrelated to the database itself, and it is not covered by any other error code--for example, a failure due to disk IO errors.</td>
<td>A request to open a database with a version lower than the one it already has. This can only happen with <ahref="/en-US/docs/Web/API/IDBOpenDBRequest"><code>IDBOpenDBRequest</code></a>.</td>
<td>The <ahref="/en-US/docs/Web/API/IndexedDB_API/Basic_Terminology#key_path">key path</a> of this index. If this attribute is null, this index is not auto-populated.</td>
<td>The <ahref="/en-US/docs/Web/API/IndexedDB_API/Basic_Terminology#key_path">key path</a> of this object store. If this attribute is set to null, then the application must provide a key for each modification operation.</td>
70
70
</tr>
71
71
<tr>
72
-
<td><code><aname="attr_mode">mode</a></code></td>
72
+
<td><code>mode</code></td>
73
73
<td><code>readonly unsigned short</code></td>
74
74
<td>The mode for isolating access to the data in this object store. For possible values, see <ahref="/en-US/docs/Web/API/IDBObjectStoreSync#constants">Constants</a>.</td>
<td>The <ahref="/en-US/docs/Web/API/IndexedDB_API/Basic_Terminology#database_connection">database connection</a> that this transaction is associated with.</td>
<p><strong>IndexedDB does not use Structured Query Language (<abbr>SQL</abbr>).</strong> It uses queries on an index that produces a cursor, which you use to iterate across the result set. If you are not familiar with NoSQL systems, read the <ahref="https://en.wikipedia.org/wiki/NoSQL">Wikipedia article on NoSQL</a>.</p>
54
54
</li>
55
55
<li>
56
-
<p><aname="origin"><strong>IndexedDB adheres to a same-origin policy</strong></a>. An origin is the domain, application layer protocol, and port of a URL of the document where the script is being executed. Each origin has its own associated set of databases. Every database has a name that identifies it within an origin.</p>
56
+
<p><strong>IndexedDB adheres to a same-origin policy</strong>. An origin is the domain, application layer protocol, and port of a URL of the document where the script is being executed. Each origin has its own associated set of databases. Every database has a name that identifies it within an origin.</p>
57
57
58
58
<p>The security boundary imposed on IndexedDB prevents applications from accessing data with a different origin. For example, while an app or a page in <ahref="https://www.example.com/app/">http://www.example.com/app/</a> can retrieve data from <ahref="https://www.example.com/dir/">http://www.example.com/dir/</a>, because they have the same origin, it cannot retrieve data from <ahref="https://www.example.com:8080/dir/">http://www.example.com:8080/dir/</a> (different port) or <aclass="link-https" href="https://www.example.com/dir/">https://www.example.com/dir/</a> (different protocol), because they have different origins.</p>
0 commit comments