aboutsummaryrefslogtreecommitdiff
path: root/files/ja/web/api/file_handle_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_handle_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_handle_api')
-rw-r--r--files/ja/web/api/file_handle_api/index.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/files/ja/web/api/file_handle_api/index.html b/files/ja/web/api/file_handle_api/index.html
index 2fa72f854f..68a8318739 100644
--- a/files/ja/web/api/file_handle_api/index.html
+++ b/files/ja/web/api/file_handle_api/index.html
@@ -188,7 +188,7 @@ IDBReq.onsuccess = function () {
}
</pre>
-<p>A file stored that way is physically put on the device. The database itself only stores a pointer to that file. It means that if the {{domxref("FileHandle")}} object is stored several times in several DBs or several data stores, all those objects will reference the same unique file. This is not a problem because to access the file, a {{domxref("LockedFile")}} object is required and operations on such object are performed in <a href="http://en.wikipedia.org/wiki/Isolation_%28database_systems%29" title="http://en.wikipedia.org/wiki/Isolation_%28database_systems%29">isolation</a>, meaning that once a {{domxref("LockedFile")}} is active, all operations of this {{domxref("LockedFile")}} are guaranteed to happen sequentially on the underlying file without being interleaved with operations from other {{domxref("LockedFile")}}.</p>
+<p>A file stored that way is physically put on the device. The database itself only stores a pointer to that file. It means that if the {{domxref("FileHandle")}} object is stored several times in several DBs or several data stores, all those objects will reference the same unique file. This is not a problem because to access the file, a {{domxref("LockedFile")}} object is required and operations on such object are performed in <a href="http://en.wikipedia.org/wiki/Isolation_%28database_systems%29">isolation</a>, meaning that once a {{domxref("LockedFile")}} is active, all operations of this {{domxref("LockedFile")}} are guaranteed to happen sequentially on the underlying file without being interleaved with operations from other {{domxref("LockedFile")}}.</p>
<h3 id="安全な書込み操作">安全な書込み操作</h3>
@@ -218,7 +218,7 @@ writing.onerror = function () {
<h3 id="FileWriter_と_API_が異なるのはなぜですか?">FileWriter と API が異なるのはなぜですか?</h3>
-<p>The <a href="http://dev.w3.org/2009/dap/file-system/file-writer.html" title="http://dev.w3.org/2009/dap/file-system/file-writer.html">FileWriter specification</a> defines FileWriters, objects aiming at representing editable files. <a href="http://lists.w3.org/Archives/Public/public-webapps/2012JanMar/0886.html" title="http://lists.w3.org/Archives/Public/public-webapps/2012JanMar/0886.html">Discussions on public-webapps</a> led to the conclusion that the API would behave poorly in the case of different entities writing concurrently to the same file. The outcome of this discussion is the FileHandle API with its LockedFile and transaction mechanism.</p>
+<p>The <a href="http://dev.w3.org/2009/dap/file-system/file-writer.html" title="http://dev.w3.org/2009/dap/file-system/file-writer.html">FileWriter specification</a> defines FileWriters, objects aiming at representing editable files. <a href="http://lists.w3.org/Archives/Public/public-webapps/2012JanMar/0886.html">Discussions on public-webapps</a> led to the conclusion that the API would behave poorly in the case of different entities writing concurrently to the same file. The outcome of this discussion is the FileHandle API with its LockedFile and transaction mechanism.</p>
<h3 id="Browser_Compatibility" name="Browser_Compatibility">仕様書</h3>