aboutsummaryrefslogtreecommitdiff
path: root/files/ja/web/api/file_and_directory_entries_api
diff options
context:
space:
mode:
authorPeter Bengtsson <mail@peterbe.com>2021-08-02 22:42:50 -0400
committerGitHub <noreply@github.com>2021-08-03 11:42:50 +0900
commitb3400a41e5ff084784e4557bb07c0a351a34d477 (patch)
tree777b9536d6076b57d63328a61d99d4a8a8b6a811 /files/ja/web/api/file_and_directory_entries_api
parentc372556f6b6e736496dce8f62f8ca346496c3e93 (diff)
downloadtranslated-content-b3400a41e5ff084784e4557bb07c0a351a34d477.tar.gz
translated-content-b3400a41e5ff084784e4557bb07c0a351a34d477.tar.bz2
translated-content-b3400a41e5ff084784e4557bb07c0a351a34d477.zip
remove link 'title' attributes that's just the 'href' (ja, part 4) (#1851)
Diffstat (limited to 'files/ja/web/api/file_and_directory_entries_api')
-rw-r--r--files/ja/web/api/file_and_directory_entries_api/introduction/index.html6
1 files changed, 3 insertions, 3 deletions
diff --git a/files/ja/web/api/file_and_directory_entries_api/introduction/index.html b/files/ja/web/api/file_and_directory_entries_api/introduction/index.html
index f99c71bbd0..134ac21270 100644
--- a/files/ja/web/api/file_and_directory_entries_api/introduction/index.html
+++ b/files/ja/web/api/file_and_directory_entries_api/introduction/index.html
@@ -52,7 +52,7 @@ translation_of: Web/API/File_and_Directory_Entries_API/Introduction
<ul>
<li>The File and Directory Entries API offers client-side storage for use cases that are not addressed by databases. If you want to have large mutable chunks of data, the File and Directory Entries API is a much more efficient storage solution than a database.</li>
<li>While Firefox supports blob storage for IndexedDB, Chrome currently does not (Chrome is still implementing support for blob storage in IndexedDB). If you are targeting Chrome for your app and you want to store blobs, the File and Directory Entries API and App Cache are your only choices. However, AppCache storage isn't locally mutable, and doesn't allow for fine-grained client-side management.</li>
- <li>In Chrome, you can use the File and Directory Entries API with the <a class="external" href="http://code.google.com/chrome/whitepapers/storage.html" title="http://code.google.com/chrome/whitepapers/storage.html">Quota Management API</a>, which lets you ask for more storage and manage your storage quota.</li>
+ <li>In Chrome, you can use the File and Directory Entries API with the <a class="external" href="http://code.google.com/chrome/whitepapers/storage.html">Quota Management API</a>, which lets you ask for more storage and manage your storage quota.</li>
</ul>
<h3 id="sample" name="sample">Sample use cases</h3>
@@ -169,7 +169,7 @@ translation_of: Web/API/File_and_Directory_Entries_API/Introduction
<p>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 file systems.</p>
-<p>The security boundary imposed on file system prevents applications from accessing data with a different origin. This protects private data by preventing access and deletion. For example, while an app or a page in <a href="http://www.example.com/app/" rel="external" title="http://www.example.com/app/">http://www.example.com/app/</a> can access files from <a href="http://www.example.com/dir/" rel="external" title="http://www.example.com/dir/">http://www.example.com/dir/</a>, because they have the same origin, it cannot retrieve files from <a href="http://www.example.com:8080/dir/" rel="external" title="http://www.example.com:8080/dir/">http://www.example.com:8080/dir/</a> (different port) or <a href="https://www.example.com/dir/" rel="external" title="https://www.example.com/dir/">https://www.example.com/dir/</a> (different protocol).</p>
+<p>The security boundary imposed on file system prevents applications from accessing data with a different origin. This protects private data by preventing access and deletion. For example, while an app or a page in <a href="http://www.example.com/app/" rel="external" title="http://www.example.com/app/">http://www.example.com/app/</a> can access files from <a href="http://www.example.com/dir/" rel="external" title="http://www.example.com/dir/">http://www.example.com/dir/</a>, because they have the same origin, it cannot retrieve files from <a href="http://www.example.com:8080/dir/" rel="external" title="http://www.example.com:8080/dir/">http://www.example.com:8080/dir/</a> (different port) or <a href="https://www.example.com/dir/" rel="external">https://www.example.com/dir/</a> (different protocol).</p>
<h3 id="execute" name="execute">The File and Directory Entries API does not let you create and rename executable files</h3>
@@ -243,5 +243,5 @@ translation_of: Web/API/File_and_Directory_Entries_API/Introduction
<ul>
<li><a href="/en-US/docs/Web/API/File_and_Directory_Entries_API">File and Directory Entries API</a></li>
- <li><a class="external" href="http://www.html5rocks.com/en/tutorials/file/filesystem/" title="http://www.html5rocks.com/en/tutorials/file/filesystem/">Exploring the FileSystem APIs</a> (HTML5 Rocks)</li>
+ <li><a class="external" href="http://www.html5rocks.com/en/tutorials/file/filesystem/">Exploring the FileSystem APIs</a> (HTML5 Rocks)</li>
</ul>