Dependent specifications may consider this API a
-[=powerful feature=]. However, unlike other [=powerful features=] whose
-[=permission request algorithm=] may throw, [=/file system entry=]'s
-[=file system entry/query access=] and [=file system entry/request access=]
-algorithms must run [=in parallel=] on the [=file system queue=] and are
-therefore not allowed to throw. Instead, the caller is expected to
-[=queue a storage task=] to [=/reject=], as appropriate,
-should these algorithms return an [=file system access result/error name=]
-other than the empty string.
-
-Note: Implementations that only implement this specification and not dependent
-specifications do not need to bother implementing [=/file system entry=]'s
-[=file system entry/query access=] and [=file system entry/request access=].
-
-Issue(101): Make access check algorithms associated with a FileSystemHandle.
-
Each [=/file system entry=] has an associated name (a [=string=]).
A valid file name is a [=string=] that is not an empty string, is not equal to "." or "..",
@@ -266,6 +218,20 @@ a [=/file system locator=] |b| if
|a|'s [=file system locator/root=] is |b|'s [=file system locator/root=], and
|a|'s [=file system locator/path=] is [=the same path as=] |b|'s [=file system locator/path=].
+A [=/file system locator=]
+is in a bucket file system
+if the first [=list/item=] of its
+[=file system locator/path=] is the empty string.
+
+Note: This is a bit magical, but it works since only the root directory of a
+[=/bucket file system=] can have a [=file system locator/path=] which
+[=list/contains=] an empty string. See {{StorageManager/getDirectory()}}.
+All other [=list/item=]s of a [=file system locator/path=] will be a
+[=valid file name=].
+
+Issue(109): Consider improving this situation by giving each locator a
+[=storage bucket=].
+
The
locate an entry algorithm given a
[=/file system locator=] |locator| runs an [=implementation-defined=] series of steps adhering to
@@ -318,6 +284,62 @@ with the website process. The [=/file system path=] might contain components
which are not known to the website unless the [=/file system locator=] is later
[=file system locator/resolved=] relative to a parent [=directory locator=].
+
+QueryFileSystemAccess(|locator|, |mode|)
+runs these steps, unless specified otherwise:
+
+1. Assert: |locator| is a [=/file system locator=].
+1. Assert: |mode| is "`read`" or "`readwrite`".
+1. If |locator| [=file system locator/is in a bucket file system=]
+ return a [=/file system access result=] with
+ a [=file system access result/permission state=]
+ of "{{PermissionState/granted}}" and with
+ an [=file system access result/error name=] of the empty string.
+1. Otherwise return a [=/file system access result=] with
+ a [=file system access result/permission state=]
+ of "{{PermissionState/denied}}" and with
+ an [=file system access result/error name=] of the empty string.
+
+Note: These steps have to be run on the [=file system queue=].
+
+
+
+
RequestFileSystemAccess(|locator|, |mode|)
+returns [$QueryFileSystemAccess$](|locator|, |mode|),
+unless specified otherwise.
+
+Note: Dependent specifications may override
+[$QueryFileSystemAccess$] and [$RequestFileSystemAccess$].
+
+A
file system access result is a [=struct=] encapsulating the
+result of running [$QueryFileSystemAccess$] or [$RequestFileSystemAccess$].
+It has the following [=struct/items=]:
+
+:
permission state
+:: A {{PermissionState}}
+:
error name
+:: A [=string=] which must be the empty string if
+ [=file system access result/permission state=] is
+ "{{PermissionState/granted}}"; otherwise an
+ [=DOMException/name=] listed in the
`DOMException` names table.
+ It is expected that in most cases when
+ [=file system access result/permission state=] is not
+ "{{PermissionState/granted}}", this should be "{{NotAllowedError}}".
+
+
Dependent specifications may consider this API a
+[=powerful feature=]. However, unlike other [=powerful features=] whose
+[=permission request algorithm=] may throw,
+[$QueryFileSystemAccess$] and [$RequestFileSystemAccess$]
+each must run [=in parallel=] on the [=file system queue=] and are
+therefore not allowed to throw. Instead, the caller is expected to
+[=queue a storage task=] to [=/reject=], as appropriate,
+should these algorithms return an [=file system access result/error name=]
+other than the empty string.
+
+
To check whether a website can access a
+{{FileSystemHandle}} |handle| with |mode|, run
+[$QueryFileSystemAccess$](|handle|'s [=FileSystemHandle/permission root locator=], |mode|).
+
## The {{FileSystemHandle}} interface ## {#api-filesystemhandle}
<![CDATA[
@@ -335,25 +357,19 @@ interface FileSystemHandle {
};
]]>
-A {{FileSystemHandle}} object is associated with a
locator (a
-[=/file system locator=]).
+A {{FileSystemHandle}} object is associated with
+a
locator (a [=/file system locator=])
+that describes the location in the file system this handle corresponds to and
+a
permission root locator (a [=/file system locator=])
+used for querying and requesting permission to use this handle.
Note: Multiple {{FileSystemHandle}} objects can have
[=the same locator as|the same=] [=/file system locator=].
A {{FileSystemHandle}}
is in a bucket file system
-if the first [=list/item=] of its [=FileSystemHandle/locator=]'s
-[=file system locator/path=] is the empty string.
-
-Note: This is a bit magical, but it works since only the root directory of a
-[=/bucket file system=] can have a [=file system locator/path=] which
-[=list/contains=] an empty string. See {{StorageManager/getDirectory()}}.
-All other [=list/item=]s of a [=file system locator/path=] will be a
-[=valid file name=].
-
-Issue(109): Consider improving this situation by giving each locator a
-[=storage bucket=].
+if its [=FileSystemHandle/locator=]
+[=file system locator/is in a bucket file system=].
{{FileSystemHandle}} objects are [=serializable objects=].
@@ -362,6 +378,8 @@ Their [=serialization steps=], given |value|, |serialized| and forSt
1. Set |serialized|.\[[Origin]] to |value|'s [=relevant settings object=]'s [=environment settings object/origin=].
1. Set |serialized|.\[[Locator]] to |value|'s [=FileSystemHandle/locator=].
+1. Set |serialized|.\[[PermissionRootLocator]] to |value|'s
+ [=FileSystemHandle/permission root locator=].
@@ -372,6 +390,7 @@ Their [=deserialization steps=], given |serialized| and |value| are:
|value|'s [=relevant settings object=]'s [=environment settings object/origin=],
then [=throw=] a "{{DataCloneError}}" {{DOMException}}.
1. Set |value|'s [=FileSystemHandle/locator=] to |serialized|.\[[Locator]].
+1. Set |value|'s [=FileSystemHandle/permission root locator=] to |serialized|.\[[PermissionRootLocator]].