From e9eb9ea063d11f698a9fb111798162de0200c27a Mon Sep 17 00:00:00 2001 From: "Michael[tm] Smith" Date: Tue, 29 Jun 2021 15:22:22 +0900 Subject: [PATCH 1/5] Ensure stable IDs for dfn refs in domintro sections MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This change ensures that dfn references/links inside sections which follow the class=domintro convention are output with IDs ending with “-dev” — and most likely, without any additional ①, ②, etc., suffix. Otherwise, without this change, dfn references/links inside class=domintro sections are output with IDs of the form “ref-foo-①”, etc. — just as the IDs output for such references/links outside of class=domintro sections. So this change helps make it likely that dfn references/links inside class=domintro sections end up with stable IDs useful for referencing from MDN and other places — rather than “ref-foo-②”, etc. IDs that might change if some new reference to a term is added to a spec somewhere preceding a class=domintro section where the term is referenced. Relates to https://github.com/mdn/browser-compat-data/issues/11088 --- bikeshed/dfnpanels.py | 5 ++++- bikeshed/h/dom.py | 2 +- bikeshed/unsortedJunk.py | 5 ++++- 3 files changed, 9 insertions(+), 3 deletions(-) diff --git a/bikeshed/dfnpanels.py b/bikeshed/dfnpanels.py index c9259e8443..117977a440 100644 --- a/bikeshed/dfnpanels.py +++ b/bikeshed/dfnpanels.py @@ -45,7 +45,10 @@ def addDfnPanels(doc, dfns): for i, el in enumerate(els): refID = el.get("id") if refID is None: - refID = f"ref-for-{id}" + if hasAncestor(el, lambda x: hasClass(x, "domintro")): + refID = f"{id}-dev" + else: + refID = f"ref-for-{id}" el.set("id", safeID(doc, refID)) if i == 0: appendChild( diff --git a/bikeshed/h/dom.py b/bikeshed/h/dom.py index 162c928685..02d15d6366 100644 --- a/bikeshed/h/dom.py +++ b/bikeshed/h/dom.py @@ -803,7 +803,7 @@ def dedupIDs(doc): continue if el.get("data-silently-dedup") is not None: warnAboutDupes = False - if dupeId.startswith("ref-for-"): + if dupeId.startswith("ref-for-") or dupeId.endswith("-dev"): warnAboutDupes = False # Try to de-dup the id by appending an integer after it. if warnAboutDupes: diff --git a/bikeshed/unsortedJunk.py b/bikeshed/unsortedJunk.py index 637fdab16a..25bccf55d6 100644 --- a/bikeshed/unsortedJunk.py +++ b/bikeshed/unsortedJunk.py @@ -1078,7 +1078,10 @@ def decorateAutolink(doc, el, linkType, linkText, ref): if el.get("id") is None: _, _, id = ref.url.partition("#") if id: - el.set("id", f"ref-for-{id}") + if hasAncestor(el, lambda x: hasClass(x, "domintro")): + el.set("id", f"{id}-dev") + else: + el.set("id", f"ref-for-{id}") el.set("data-silently-dedup", "") # Get all the values that the type expands to, add it as a title. From 3ce8770151f22aa4c7fb0fe7d69106e400830b1c Mon Sep 17 00:00:00 2001 From: "Michael[tm] Smith" Date: Tue, 29 Jun 2021 20:10:43 +0900 Subject: [PATCH 2/5] Update tests --- tests/github/WICG/app-history/spec.html | 286 +- tests/github/WICG/cookie-store/index.html | 108 +- .../github/WICG/file-system-access/index.html | 568 +-- tests/github/WICG/kv-storage/spec.html | 174 +- .../github/WICG/local-font-access/index.html | 68 +- .../WICG/shape-detection-api/index-zh-cn.html | 68 +- .../WICG/shape-detection-api/index.html | 156 +- .../github/WICG/shape-detection-api/text.html | 22 +- tests/github/WICG/web-locks/index.html | 110 +- tests/github/w3c/FileAPI/index.html | 190 +- tests/github/w3c/IndexedDB/index.html | 2468 ++++----- .../github/w3c/mediacapture-image/index.html | 928 ++-- .../mediacapture-record/MediaRecorder.html | 656 +-- tests/github/whatwg/dom/dom.html | 4494 ++++++++--------- tests/github/whatwg/encoding/encoding.html | 598 +-- tests/github/whatwg/fetch/fetch.html | 512 +- .../github/whatwg/fullscreen/fullscreen.html | 102 +- tests/github/whatwg/streams/index.html | 2040 ++++---- tests/github/whatwg/xhr/xhr.html | 712 +-- 19 files changed, 7130 insertions(+), 7130 deletions(-) diff --git a/tests/github/WICG/app-history/spec.html b/tests/github/WICG/app-history/spec.html index 1d075ed239..954f95d310 100644 --- a/tests/github/WICG/app-history/spec.html +++ b/tests/github/WICG/app-history/spec.html @@ -731,20 +731,20 @@

1.
-
appHistory . current +
appHistory . current
-

The current AppHistoryEntry.

-
appHistory . entries() +

The current AppHistoryEntry.

+
appHistory . entries()
-

Returns an array of AppHistoryEntry instances representing the current app history list, i.e. all session history entries for this Window that are same origin and contiguous to the current session history entry.

-
appHistory . canGoBack +

Returns an array of AppHistoryEntry instances representing the current app history list, i.e. all session history entries for this Window that are same origin and contiguous to the current session history entry.

+
appHistory . canGoBack
-

Returns true if the current AppHistoryEntry is not the first one in the app history entries list.

-
appHistory . canGoForward +

Returns true if the current AppHistoryEntry is not the first one in the app history entries list.

+
appHistory . canGoForward
-

Returns true if the current AppHistoryEntry is not the last one in the app history entries list.

+

Returns true if the current AppHistoryEntry is not the last one in the app history entries list.

-

Each AppHistory object has an associated entry list, a list of AppHistoryEntry objects, initially empty.

+

Each AppHistory object has an associated entry list, a list of AppHistoryEntry objects, initially empty.

Each AppHistory object has an associated current index, an integer, initially −1.

The current getter steps are: @@ -840,7 +840,7 @@

1.

Let she be sessionHistory[backwardIndex].

  • -

    If she’s origin is same origin with currentSHE’s origin, then prepend she to appHistorySHEs.

    +

    If she’s origin is same origin with currentSHE’s origin, then prepend she to appHistorySHEs.

  • Otherwise, break.

  • @@ -856,7 +856,7 @@

    1.

    Let she be sessionHistory[forwardIndex].

  • -

    If she’s origin is same origin with currentSHE’s origin, then append she to appHistorySHEs.

    +

    If she’s origin is same origin with currentSHE’s origin, then append she to appHistorySHEs.

  • Otherwise, break.

  • @@ -878,12 +878,12 @@

    1. For each she of appHistorySHEs:

    1. -

      If appHistory’s entry list contains an AppHistoryEntry existingAHE whose session history entry is she, then append existingAHE to newEntryList.

      +

      If appHistory’s entry list contains an AppHistoryEntry existingAHE whose session history entry is she, then append existingAHE to newEntryList.

    2. Otherwise:

      1. -

        Let newAHE be a new AppHistoryEntry created in the relevant realm of appHistory.

        +

        Let newAHE be a new AppHistoryEntry created in the relevant realm of appHistory.

      2. Set newAHE’s session history entry to she.

      3. @@ -899,7 +899,7 @@

        1.

        Set appHistory’s current index to newCurrentIndex.

      -

      For same-document navigations only the current index and the indices of the various AppHistoryEntry objects will ultimately be updated by this algorithm. Implementations can special-case same-document navigations and avoid reassembling the entry list.

      +

      For same-document navigations only the current index and the indices of the various AppHistoryEntry objects will ultimately be updated by this algorithm. Implementations can special-case same-document navigations and avoid reassembling the entry list. 

    • [Exposed=Window]
@@ -936,40 +936,40 @@
    -

    A FileSystemDirectoryHandle's associated entry must be a directory entry.

    -

    FileSystemDirectoryHandle objects are serializable objects. Their serialization steps and deserialization steps are the same as those for FileSystemHandle.

    +

    A FileSystemDirectoryHandle's associated entry must be a directory entry.

    +

    FileSystemDirectoryHandle objects are serializable objects. Their serialization steps and deserialization steps are the same as those for FileSystemHandle.

    In the Origin Trial as available in Chrome 78, these objects are not yet serializable. In Chrome 82 they are.

    In Chrome versions upto Chrome 85 getFileHandle and getDirectoryHandle where @@ -1492,10 +1492,10 @@

    In the future we might want to add arguments to the async iterable declaration to support for example recursive iteration. <https://github.com/wicg/file-system-access/issues/173>

    - The asynchronous iterator initialization steps for a FileSystemDirectoryHandle handle ant its async iterator iterator are: + The asynchronous iterator initialization steps for a FileSystemDirectoryHandle handle ant its async iterator iterator are:
    1. -

      Let permissionStatus be the result of querying file system permission given handle and "read".

      +

      Let permissionStatus be the result of querying file system permission given handle and "read".

    2. If permissionStatus is not "granted", throw a NotAllowedError.

      @@ -1504,20 +1504,20 @@

      - To get the next iteration result for a FileSystemDirectoryHandle handle and its async iterator iterator: + To get the next iteration result for a FileSystemDirectoryHandle handle and its async iterator iterator:

      1. Let promise be a new promise.

      2. Let directory be handle’s entry.

      3. -

        Let permissionStatus be the result of querying file system permission given handle and "read".

        +

        Let permissionStatus be the result of querying file system permission given handle and "read".

      4. If permissionStatus is not "granted", reject promise with a NotAllowedError and return promise.

      5. Let child be an entry in directory’s children, - such that child’s name is not contained in iterator’s past results, + such that child’s name is not contained in iterator’s past results, or null if no such entry exists.

        Note: This is intentionally very vague about the iteration order. Different platforms and file systems provide different guarantees about iteration order, and we want it to @@ -1533,21 +1533,21 @@

        Append child’s name to iterator’s past results.

        +

        Append child’s name to iterator’s past results.

      6. If child is a file entry:

        1. -

          Let result be a new FileSystemFileHandle associated with child.

          +

          Let result be a new FileSystemFileHandle associated with child.

      7. Otherwise:

        1. -

          Let result be a new FileSystemDirectoryHandle associated with child.

          +

          Let result be a new FileSystemDirectoryHandle associated with child.

      8. -

        Resolve promise with (child’s name, result).

        +

        Resolve promise with (child’s name, result).

    3. Return promise.

      @@ -1585,12 +1585,12 @@

      -
      fileHandle = await directoryHandle . getFileHandle(name) -
      fileHandle = await directoryHandle . getFileHandle(name, { create: false }) +
      fileHandle = await directoryHandle . getFileHandle(name) +
      fileHandle = await directoryHandle . getFileHandle(name, { create: false })

      Returns a handle for a file named name in the directory represented by directoryHandle. If no such file exists, this rejects.

      -
      fileHandle = await directoryHandle . getFileHandle(name, { create: true }) +
      fileHandle = await directoryHandle . getFileHandle(name, { create: true })

      Returns a handle for a file named name in the directory represented by directoryHandle. If no such file exists, this creates a new file. If no file with named name can be created this @@ -1600,7 +1600,7 @@

      create: false }.

      + with { create: false }.

    @@ -1617,17 +1617,17 @@

    this’s entry.

  • -

    If options.create is true:

    +

    If options.create is true:

    1. -

      Let permissionStatus be the result of requesting file system permission given this and "readwrite". +

      Let permissionStatus be the result of requesting file system permission given this and "readwrite". If that throws an exception, reject result with that exception and abort.

  • Otherwise:

    1. -

      Let permissionStatus be the result of querying file system permission given this and "read".

      +

      Let permissionStatus be the result of querying file system permission given this and "read".

  • If permissionStatus is not "granted", @@ -1636,7 +1636,7 @@

    For each child of entry’s children:

    1. -

      If child’s name equals name:

      +

      If child’s name equals name:

      1. If child is a directory entry:

        @@ -1645,11 +1645,11 @@

        Reject result with a TypeMismatchError and abort.

    2. -

      Resolve result with a new FileSystemFileHandle whose entry is child and abort.

      +

      Resolve result with a new FileSystemFileHandle whose entry is child and abort.

  • -

    If options.create is false:

    +

    If options.create is false:

    1. Reject result with a NotFoundError and abort.

      @@ -1657,7 +1657,7 @@

      file entry.

    2. -

      Set child’s name to name.

      +

      Set child’s name to name.

    3. Set child’s binary data to an empty byte sequence.

    4. @@ -1668,7 +1668,7 @@

      reject result with that exception and abort.

      Better specify what possible exceptions this could throw. <https://github.com/wicg/file-system-access/issues/68>

    5. -

      Resolve result with a new FileSystemFileHandle whose entry is child.

      +

      Resolve result with a new FileSystemFileHandle whose entry is child.

  • Return result.

    @@ -1677,11 +1677,11 @@

    2.5.3. The getDirectoryHandle() method

    -
    subdirHandle = await directoryHandle . getDirectoryHandle(name) -
    subdirHandle = await directoryHandle . getDirectoryHandle(name, { create: false }) +
    subdirHandle = await directoryHandle . getDirectoryHandle(name) +
    subdirHandle = await directoryHandle . getDirectoryHandle(name, { create: false })

    Returns a handle for a directory named name in the directory represented by directoryHandle. If no such directory exists, this rejects.

    -
    subdirHandle = await directoryHandle . getDirectoryHandle(name, { create: true }) +
    subdirHandle = await directoryHandle . getDirectoryHandle(name, { create: true })

    Returns a handle for a directory named name in the directory represented by directoryHandle. If no such directory exists, this creates a new directory. If creating the directory failed, this rejects. Creation can fail because there already is a file with the same @@ -1690,7 +1690,7 @@

    create: false }.

    + with { create: false }.

    @@ -1723,17 +1723,17 @@

    this’s entry.

  • -

    If options.create is true:

    +

    If options.create is true:

    1. -

      Let permissionStatus be the result of requesting file system permission given this and "readwrite". +

      Let permissionStatus be the result of requesting file system permission given this and "readwrite". If that throws an exception, reject result with that exception and abort.

  • Otherwise:

    1. -

      Let permissionStatus be the result of querying file system permission given this and "read".

      +

      Let permissionStatus be the result of querying file system permission given this and "read".

  • If permissionStatus is not "granted", @@ -1742,7 +1742,7 @@

    For each child of entry’s children:

    1. -

      If child’s name equals name:

      +

      If child’s name equals name:

      1. If child is a file entry:

        @@ -1751,11 +1751,11 @@

        Reject result with a TypeMismatchError and abort.

    2. -

      Resolve result with a new FileSystemDirectoryHandle whose entry is child and abort.

      +

      Resolve result with a new FileSystemDirectoryHandle whose entry is child and abort.

  • -

    If options.create is false:

    +

    If options.create is false:

    1. Reject result with a NotFoundError and abort.

      @@ -1763,7 +1763,7 @@

      directory entry.

    2. -

      Set child’s name to name.

      +

      Set child’s name to name.

    3. Set child’s children to an empty set.

    4. @@ -1772,7 +1772,7 @@

      reject result with that exception and abort.

      Better specify what possible exceptions this could throw. <https://github.com/wicg/file-system-access/issues/68>

    5. -

      Resolve result with a new FileSystemDirectoryHandle whose entry is child.

      +

      Resolve result with a new FileSystemDirectoryHandle whose entry is child.

  • Return result.

    @@ -1797,14 +1797,14 @@

    -
    await directoryHandle . removeEntry(name) -
    await directoryHandle . removeEntry(name, { recursive: false }) +
    await directoryHandle . removeEntry(name) +
    await directoryHandle . removeEntry(name, { recursive: false })

    If the directory represented by directoryHandle contains a file named name, or an empty directory named name, this will attempt to delete that file or directory.

    Attempting to delete a file or directory that does not exist is considered success, while attempting to delete a non-empty directory will result in a promise rejection.

    -
    await directoryHandle . removeEntry(name, { recursive: true }) +
    await directoryHandle . removeEntry(name, { recursive: true })

    Removes the entry named name in the directory represented by directoryHandle. If that entry is a directory, its contents will also be deleted recursively. @@ -1826,7 +1826,7 @@

    this’s entry.

  • -

    Let permissionStatus be the result of requesting file system permission given this and "readwrite". +

    Let permissionStatus be the result of requesting file system permission given this and "readwrite". If that throws an exception, reject result with that exception and abort.

  • If permissionStatus is not "granted", @@ -1835,13 +1835,13 @@

    For each child of entry’s children:

    1. -

      If child’s name equals name:

      +

      If child’s name equals name:

      1. If child is a directory entry:

        1. -

          If child’s children is not empty and options.recursive is false:

          +

          If child’s children is not empty and options.recursive is false:

          1. Reject result with an InvalidModificationError and abort.

            @@ -1851,7 +1851,7 @@

            Remove child from entry’s children.

          2. If removing child in the underlying file system throws an exception, reject result with that exception and abort.

            -

            Note: If recursive is true, the removal can fail +

            Note: If recursive is true, the removal can fail non-atomically. Some files or directories might have been removed while other files or directories still exist.

            Better specify what possible exceptions this could throw. <https://github.com/wicg/file-system-access/issues/68>

            @@ -1869,7 +1869,7 @@

            2.5.5. The resolve() method

            -
            path = await directory . resolve( child ) +
            path = await directory . resolve( child )

            If child is equal to directory, path will be an empty array.

            @@ -1949,7 +1949,7 @@

            The resolve(possibleDescendant) method, when invoked, must return the result of resolving possibleDescendant’s entry relative to this's entry.

            -

            2.6. The FileSystemWritableFileStream interface

            +

            2.6. The FileSystemWritableFileStream interface

            enum WriteCommandType {
   "write",
   "seek",
@@ -1972,30 +1972,30 @@ 
            Promise<undefined> truncate(unsigned long long size);
 };
            -

            A FileSystemWritableFileStream has an associated [[file]] (a file entry).

            -

            A FileSystemWritableFileStream has an associated [[buffer]] (a byte sequence). +

            A FileSystemWritableFileStream has an associated [[file]] (a file entry).

            +

            A FileSystemWritableFileStream has an associated [[buffer]] (a byte sequence). It is initially empty.

            Note: This buffer can get arbitrarily large, so it is expected that implementations will not keep this in memory, but instead use a temporary file for this. All access to [[buffer]] is done in promise returning methods and algorithms, so even though operations on it seem sync, implementations can implement them async.

            -

            A FileSystemWritableFileStream has an associated [[seekOffset]] (a number). +

            A FileSystemWritableFileStream has an associated [[seekOffset]] (a number). It is initially 0.

            - A FileSystemWritableFileStream object is a WritableStream object with additional + A FileSystemWritableFileStream object is a WritableStream object with additional convenience methods, which operates on a single file on disk.

            Upon creation, an underlying sink will have been created and the stream will be usable. All operations executed on the stream are queuable and producers will be able to respond to backpressure.

            -

            The underlying sink’s write method, and therefore WritableStreamDefaultWriter’s write() method, will accept byte-like data or WriteParams as input.

            -

            The FileSystemWritableFileStream has a file position cursor initialized at byte offset 0 from the top of the file. -When using write() or by using WritableStream capabilities through the WritableStreamDefaultWriter’s write() method, this position will be advanced based on the number of bytes written through the stream object.

            -

            Similarly, when piping a ReadableStream into a FileSystemWritableFileStream object, this position is updated with the number of bytes that passed through the stream.

            -

            getWriter() returns an instance of WritableStreamDefaultWriter.

            +

            The underlying sink’s write method, and therefore WritableStreamDefaultWriter’s write() method, will accept byte-like data or WriteParams as input.

            +

            The FileSystemWritableFileStream has a file position cursor initialized at byte offset 0 from the top of the file. +When using write() or by using WritableStream capabilities through the WritableStreamDefaultWriter’s write() method, this position will be advanced based on the number of bytes written through the stream object.

            +

            Similarly, when piping a ReadableStream into a FileSystemWritableFileStream object, this position is updated with the number of bytes that passed through the stream.

            +

            getWriter() returns an instance of WritableStreamDefaultWriter.

            To create a new FileSystemWritableFileStream given a file entry file in a Realm realm, perform the following steps:
            1. -

              Let stream be a new FileSystemWritableFileStream in realm.

              +

              Let stream be a new FileSystemWritableFileStream in realm.

            2. Set stream.[[file]] to file.

            3. @@ -2010,8 +2010,8 @@

              in parallel:

              1. -

                Let permissionStatus be the permission state for a FileSystemPermissionDescriptor with handle representing stream.[[file]], - and mode = "readwrite".

                +

                Let permissionStatus be the permission state for a FileSystemPermissionDescriptor with handle representing stream.[[file]], + and mode = "readwrite".

              2. If permissionStatus is not "granted", reject closeResult with a NotAllowedError and abort.

                @@ -2041,7 +2041,7 @@

                The write a chunk algorithm, -given a FileSystemWritableFileStream stream and chunk, +given a FileSystemWritableFileStream stream and chunk, runs these steps:
                1. @@ -2053,19 +2053,19 @@

                  in parallel:

                  1. -

                    Let permissionStatus be the permission state for a FileSystemPermissionDescriptor with handle representing stream.[[file]], - and mode = "readwrite".

                    +

                    Let permissionStatus be the permission state for a FileSystemPermissionDescriptor with handle representing stream.[[file]], + and mode = "readwrite".

                  2. If permissionStatus is not "granted", reject p with a NotAllowedError and abort.

                  3. -

                    Let command be input.type if input is a WriteParams, +

                    Let command be input.type if input is a WriteParams, and "write" otherwise.

                  4. If command is "write":

                    1. -

                      Let data be input.data if input is a WriteParams, +

                      Let data be input.data if input is a WriteParams, and input otherwise.

                    2. If data is undefined, @@ -2073,7 +2073,7 @@

                      [[seekOffset]].

                    3. -

                      If input is a WriteParams and input.position is not undefined, +

                      If input is a WriteParams and input.position is not undefined, set writePosition to input.position.

                    4. Let oldSize be stream.[[buffer]]'s length.

                      @@ -2175,30 +2175,30 @@

                      2.6.1. The write() method

                      +

                      2.6.1. The write() method

                      -
                      await stream . write(data) -
                      await stream . write({ type: "write", data: data }) +
                      await stream . write(data) +
                      await stream . write({ type: "write", data: data })

                      Writes the content of data into the file associated with stream at the current file cursor offset.

                      No changes are written to the actual file on disk until the stream has been closed. Changes are typically written to a temporary file instead.

                      -
                      await stream . write({ type: "write", position: position, data: data }) +
                      await stream . write({ type: "write", position: position, data: data })

                      Writes the content of data into the file associated with stream at position bytes from the top of the file. Also updates the current file cursor offset to the end of the written data.

                      No changes are written to the actual file on disk until the stream has been closed. Changes are typically written to a temporary file instead.

                      -
                      await stream . write({ type: "seek", position: position }) +
                      await stream . write({ type: "seek", position: position })

                      Updates the current file cursor offset the position bytes from the top of the file.

                      -
                      await stream . write({ type: "truncate", size: size }) +
                      await stream . write({ type: "truncate", size: size })

                      Resizes the file associated with stream to be size bytes long. If size is larger than the current file size this pads the file with null bytes, otherwise it truncates the file.

                      -

                      The file cursor is updated when truncate is called. If the offset is smaller than offset, +

                      The file cursor is updated when truncate is called. If the offset is smaller than offset, it remains unchanged. If the offset is larger than size, the offset is set to size to ensure that subsequent writes do not error.

                      No changes are written to the actual file until on disk until the stream has been closed. @@ -2222,7 +2222,7 @@

                      2.6.2. The seek() method

                      -
                      await stream . seek(position) +
                      await stream . seek(position)

                      Updates the current file cursor offset the position bytes from the top of the file.

                      @@ -2235,7 +2235,7 @@

                      getting a writer for this.

                    5. Let result be the result of writing a chunk to writer given - «[ "type" → "seek", "position" → position ]».

                      + «[ "type" → "seek", "position" → position ]».

                    6. Release writer.

                    7. @@ -2245,11 +2245,11 @@

                      2.6.3. The truncate() method

                      -
                      await stream . truncate(size) +
                      await stream . truncate(size)

                      Resizes the file associated with stream to be size bytes long. If size is larger than the current file size this pads the file with null bytes, otherwise it truncates the file.

                      -

                      The file cursor is updated when truncate is called. If the offset is smaller than offset, +

                      The file cursor is updated when truncate is called. If the offset is smaller than offset, it remains unchanged. If the offset is larger than size, the offset is set to size to ensure that subsequent writes do not error.

                      No changes are written to the actual file until on disk until the stream has been closed. @@ -2264,7 +2264,7 @@

                      getting a writer for this.

                    8. Let result be the result of writing a chunk to writer given - «[ "type" → "truncate", "size" → size ]».

                      + «[ "type" → "truncate", "size" → size ]».

                    9. Release writer.

                    10. @@ -2294,9 +2294,9 @@

                      SecureContext] partial interface Window { - Promise<sequence<FileSystemFileHandle>> showOpenFilePicker(optional OpenFilePickerOptions options = {}); - Promise<FileSystemFileHandle> showSaveFilePicker(optional SaveFilePickerOptions options = {}); - Promise<FileSystemDirectoryHandle> showDirectoryPicker(optional DirectoryPickerOptions options = {}); + Promise<sequence<FileSystemFileHandle>> showOpenFilePicker(optional OpenFilePickerOptions options = {}); + Promise<FileSystemFileHandle> showSaveFilePicker(optional SaveFilePickerOptions options = {}); + Promise<FileSystemDirectoryHandle> showDirectoryPicker(optional DirectoryPickerOptions options = {}); };

                      The showOpenFilePicker(), showSaveFilePicker() and showDirectoryPicker() methods @@ -2307,12 +2307,12 @@

                      In Chrome versions earlier than 85, this was implemented as a generic chooseFileSystemEntries method.

                      3.1. Local File System Permissions

                      -

                      The fact that the user picked the specific files returned by the local file system handle factories in a prompt +

                      The fact that the user picked the specific files returned by the local file system handle factories in a prompt should be treated by the user agent as the user intending to grant read access to the website -for the returned files. As such, at the time the promise returned by one of the local file system handle factories resolves, permission state for a descriptor with handle set to the returned handle, -and mode set to "read" should be "granted".

                      -

                      Additionally for calls to showSaveFilePicker the permission state for a descriptor with handle set to the returned handle, -and mode set to readwrite should be "granted".

                      +for the returned files. As such, at the time the promise returned by one of the local file system handle factories resolves, permission state for a descriptor with handle set to the returned handle, +and mode set to "read" should be "granted".

                      +

                      Additionally for calls to showSaveFilePicker the permission state for a descriptor with handle set to the returned handle, +and mode set to readwrite should be "granted".

                      To verify that an environment is allowed to show a file picker, run these steps:
                        @@ -2331,16 +2331,16 @@

                        3.2. The showOpenFilePicker() method

                        -
                        [ handle ] = await window . showOpenFilePicker() -
                        [ handle ] = await window . showOpenFilePicker({ multiple: false }) +
                        [ handle ] = await window . showOpenFilePicker() +
                        [ handle ] = await window . showOpenFilePicker({ multiple: false })

                        Shows a file picker that lets a user select a single existing file, returning a handle for the selected file.

                        -
                        handles = await window . showOpenFilePicker({ multiple: true }) +
                        handles = await window . showOpenFilePicker({ multiple: true })

                        Shows a file picker that lets a user select multiple existing files, returning handles for the selected files.

                        -

                        Additional options can be passed to showOpenFilePicker() to indicate the types of files +

                        Additional options can be passed to showOpenFilePicker() to indicate the types of files the website wants the user to select. See § 3.4 FilePickerOptions.types for details.

                        @@ -2365,7 +2365,7 @@

                        Optionally, wait until any prior execution of this algorithm has terminated.

                      1. Display a prompt to the user requesting that the user pick some files. - If options.multiple is false, there must be no more than one file selected; + If options.multiple is false, there must be no more than one file selected; otherwise any number may be selected.

                        The displayed prompt should let the user pick one of the accepts options to filter the list of displayed files. Exactly how this is implemented, and what this prompt looks like is left up to the user agent.

                        @@ -2391,7 +2391,7 @@

                        reject p with an AbortError and abort.

                    11. -

                      Add a new FileSystemFileHandle associated with entry to result.

                      +

                      Add a new FileSystemFileHandle associated with entry to result.

                  5. Perform the activation notification steps in global’s browsing context.

                    @@ -2407,13 +2407,13 @@

                    3.3. The showSaveFilePicker() method

                    -
                    handle = await window . showSaveFilePicker( options ) +
                    handle = await window . showSaveFilePicker( options )

                    Shows a file picker that lets a user select a single file, returning a handle for the selected file. The selected file does not have to exist already. If the selected file does not exist a new empty file is created before this method returns, otherwise the existing file is cleared before this method returned.

                    -

                    Additional options can be passed to showSaveFilePicker() to indicate the types of files +

                    Additional options can be passed to showSaveFilePicker() to indicate the types of files the website wants the user to select. See § 3.4 FilePickerOptions.types for details.

                    @@ -2462,7 +2462,7 @@

                    Set entry’s binary data to an empty byte sequence.

                  6. -

                    Set result to a new FileSystemFileHandle associated with entry.

                    +

                    Set result to a new FileSystemFileHandle associated with entry.

                  7. Perform the activation notification steps in global’s browsing context.

                    Note: This lets a website immediately perform operations on the returned handles that @@ -2476,13 +2476,13 @@

                    3.4. FilePickerOptions.types

                    - The showOpenFilePicker(options) and showSaveFilePicker(options) methods accept a FilePickerOptions argument, which lets the website specify the types of files + The showOpenFilePicker(options) and showSaveFilePicker(options) methods accept a FilePickerOptions argument, which lets the website specify the types of files the file picker will let the user select. -

                    Each entry in types specifies a single user selectable option +

                    Each entry in types specifies a single user selectable option for filtering the files displayed in the file picker.

                    -

                    Each option consists of an optional description and a number of MIME types and extensions (specified as a mapping of +

                    Each option consists of an optional description and a number of MIME types and extensions (specified as a mapping of MIME type to a list of extensions). If no description is provided one will be generated. -Extensions have to be strings that start with a "." and only contain valid suffix code points. +Extensions have to be strings that start with a "." and only contain valid suffix code points. Additionally extensions are limited to a length of 16 code points.

                    In addition to complete MIME types, "*" can be used as the subtype of a MIME type to match for example all image formats with "image/*".

                    @@ -2491,23 +2491,23 @@

                    By default the file picker will also include an option to not apply any filter, -letting the user select any file. Set excludeAcceptAllOption to true to not +letting the user select any file. Set excludeAcceptAllOption to true to not include this option in the file picker.

                    For example , the following options will let the user pick one of three different filters. One for text files (either plain text or HTML), one for images, and a third one that doesn’t apply any filter and lets the user select any file.

                    const options = {
-  types: [
+  types: [
     {
-      description: 'Text Files',
-      accept: {
+      description: 'Text Files',
+      accept: {
         'text/plain': ['.txt', '.text'],
         'text/html': ['.html', '.htm']
       }
     },
     {
-      description: 'Images',
-      accept: {
+      description: 'Images',
+      accept: {
         'image/*': ['.png', '.gif', '.jpeg', '.jpg']
       }
     }
@@ -2517,30 +2517,30 @@ 
                    On the other hand, the following example will only let the user select SVG files. The dialog
 will not show an option to not apply any filters.
                    
 
                    const options = {
-  types: [
+  types: [
     {
-      accept: {
+      accept: {
         'image/svg+xml': '.svg'
       }
     },
   ],
-  excludeAcceptAllOption: true
+  excludeAcceptAllOption: true
 };

                    - To process accept types, given FilePickerOptions options, + To process accept types, given FilePickerOptions options, run these steps:

                    1. Let accepts options be a empty list of pairs.

                    2. -

                      For each type of options.types:

                      +

                      For each type of options.types:

                      1. -

                        Let description be type.description.

                        +

                        Let description be type.description.

                      2. -

                        For each typeString → suffixes of type.accept:

                        +

                        For each typeString → suffixes of type.accept:

                        1. Let parsedType be the result of parse a MIME type with typeString.

                          @@ -2565,7 +2565,7 @@

                          Let filter be the following steps, given a filename (a string), and a type (a MIME type):

                          1. -

                            For each typeString → suffixes of type.accept:

                            +

                            For each typeString → suffixes of type.accept:

                          2. Let parsedType be the result of parse a MIME type with typeString.

                              @@ -2599,7 +2599,7 @@

                            1. If either accepts options is empty, -or options.excludeAcceptAllOption is false:

                              +or options.excludeAcceptAllOption is false:

                              1. Let description be a user understandable string describing "all files".

                                @@ -2622,7 +2622,7 @@

                                If suffix does not start with ".", throw a TypeError.

                              2. -

                                If suffix contains any code points that are not valid suffix code points, +

                                If suffix contains any code points that are not valid suffix code points, throw a TypeError.

                              3. If suffix ends with ".", throw a TypeError.

                                @@ -2633,7 +2633,7 @@

                                3.5. The showDirectoryPicker() method

                                -
                                handle = await window . showDirectoryPicker() +
                                handle = await window . showDirectoryPicker()

                                Shows a directory picker that lets the user select a single directory, returning a handle for the selected directory.

                                @@ -2675,7 +2675,7 @@

                                reject p with an AbortError and abort.

                            2. -

                              Set result to a new FileSystemDirectoryHandle associated with entry.

                              +

                              Set result to a new FileSystemDirectoryHandle associated with entry.

                            3. Perform the activation notification steps in global’s browsing context.

                              Note: This lets a website immediately perform operations on the returned handles that @@ -2698,9 +2698,9 @@

                              file entries and directory entries respectively.

                              -
                              handle = await item . getAsFileSystemHandle() +
                              handle = await item . getAsFileSystemHandle()
                              -

                              Returns a FileSystemFileHandle object if the dragged item is a file and a FileSystemDirectoryHandle object if the dragged item is a directory.

                              +

                              Returns a FileSystemFileHandle object if the dragged item is a file and a FileSystemDirectoryHandle object if the dragged item is a directory.

                              @@ -2723,13 +2723,13 @@

                              file entry:

                              1. -

                                Let handle be a FileSystemFileHandle associated with entry.

                                +

                                Let handle be a FileSystemFileHandle associated with entry.

                            4. Else if entry is a directory entry:

                              1. -

                                Let handle be a FileSystemDirectoryHandle associated with entry.

                                +

                                Let handle be a FileSystemDirectoryHandle associated with entry.

                            5. Resolve p with entry.

                              @@ -2765,7 +2765,7 @@

                              This currently does not block access to too sensitive or dangerous directories, to be consistent with other APIs that give access to dropped files and directories. This is inconsistent -with the local file system handle factories though, so we might want to reconsider this.

                              +with the local file system handle factories though, so we might want to reconsider this.

                              4. Accessing the Origin Private File System

                              The origin private file system is a storage endpoint whose identifier is "fileSystem", types are « "local" », and quota is null.

                              @@ -2776,14 +2776,14 @@

                              origin private file system exist.

                              [SecureContext]
 partial interface StorageManager {
-  Promise<FileSystemDirectoryHandle> getDirectory();
+  Promise<FileSystemDirectoryHandle> getDirectory();
 };

                              In Chrome this functionality was previously exposed as FileSystemDirectoryHandle.getSystemDirectory({type: "sandbox"}). This new method is available as of Chrome 85.

                              -
                              directoryHandle = await navigator . storage . getDirectory() +
                              directoryHandle = await navigator . storage . getDirectory()

                              Returns the root directory of the origin private file system.

                              @@ -2803,14 +2803,14 @@

                              Let dir be a new directory entry.

                            6. -

                              Set dir’s name to "".

                              +

                              Set dir’s name to "".

                            7. Set dir’s children to an empty set.

                            8. Set map["root"] to dir.

                          3. -

                            Return a promise resolved with a new FileSystemDirectoryHandle, +

                            Return a promise resolved with a new FileSystemDirectoryHandle, whose associated entry is map["root"].

                    @@ -2883,8 +2883,8 @@

                    6.3. First-party vs third-party contexts.

                    In third-party contexts (e.g. an iframe whose origin does not match that of the top-level frame) websites can’t gain access to data they don’t already have access to. This includes both getting -access to new files or directories via the local file system handle factories, as well as requesting -more permissions to existing handles via the requestPermission API.

                    +access to new files or directories via the local file system handle factories, as well as requesting +more permissions to existing handles via the requestPermission API.

                    Handles can also only be post-messaged to same-origin destinations. Attempts to send a handle to a cross-origin destination will result in a messageerror event.

                    7. Security Considerations

                    @@ -2914,7 +2914,7 @@

                    truncate() and writing at a +overhead). While the presence of truncate() and writing at a potentially really large offset past the end of a file makes it much easier and lower cost to create large files, on most file systems such files should not actually take up as much disk space as most commonly used file systems support sparse files (and thus wouldn’t actually store the NUL @@ -3111,7 +3111,7 @@

                    https://w3c.github.io/FileAPI/#dfn-fileReferenced in:

            -

            3.2. set(key, value)

            +

            3.2. set(key, value)

            -
            await storage.set(key, value) +
            await storage.set(key, value)

            Asynchronously stores the given value so that it can later be retrieved by the given key.

            -

            Keys have to follow the same restrictions as IndexedDB keys: roughly, a key can be a number, string, array, Date, ArrayBuffer, DataView, typed array, or an array of these. Invalid keys will cause the returned promise to reject with a "DataError" DOMException.

            -

            Values can be any value that can be structured-serialized for storage. Un-serializable values will cause a "DataCloneError" DOMException. The value undefined will cause the corresponding entry to be deleted.

            +

            Keys have to follow the same restrictions as IndexedDB keys: roughly, a key can be a number, string, array, Date, ArrayBuffer, DataView, typed array, or an array of these. Invalid keys will cause the returned promise to reject with a "DataError" DOMException.

            +

            Values can be any value that can be structured-serialized for storage. Un-serializable values will cause a "DataCloneError" DOMException. The value undefined will cause the corresponding entry to be deleted.

            The returned promise will fulfill with undefined on success.

            1. -

              If key is not allowed as a key, return a promise rejected with a "DataError" DOMException.

              +

              If key is not allowed as a key, return a promise rejected with a "DataError" DOMException.

            2. Return the result of performing a database operation given this object, "readwrite", and the following steps operating on transaction and store:

                @@ -827,17 +827,17 @@

            -

            3.3. get(key)

            +

            3.3. get(key)

            -
            value = await storage.get(key) +
            value = await storage.get(key)

            Asynchronously retrieves the value stored at the given key, or undefined if there is no value stored at key.

            -

            Values retrieved will be structured-deserialized from their original form.

            +

            Values retrieved will be structured-deserialized from their original form.

            1. -

              If key is not allowed as a key, return a promise rejected with a "DataError" DOMException.

              +

              If key is not allowed as a key, return a promise rejected with a "DataError" DOMException.

            2. Return the result of performing a database operation given this object, "readonly", and the following steps operating on transaction and store:

                @@ -854,17 +854,17 @@

            -

            3.4. delete(key)

            +

            3.4. delete(key)

            -
            await storage.delete(key) +
            await storage.delete(key)
            -

            Asynchronously deletes the entry at the given key. This is equivalent to storage.set(key, undefined).

            +

            Asynchronously deletes the entry at the given key. This is equivalent to storage.set(key, undefined).

            The returned promise will fulfill with undefined on success.

            1. -

              If key is not allowed as a key, return a promise rejected with a "DataError" DOMException.

              +

              If key is not allowed as a key, return a promise rejected with a "DataError" DOMException.

            2. Return the result of performing a database operation given this object, "readwrite", and the following steps operating on transaction and store:

                @@ -883,9 +883,9 @@

            -

            3.5. clear()

            +

            3.5. clear()

            -
            await storage.clear() +
            await storage.clear()

            Asynchronously deletes all entries in this storage area.

            This is done by actually deleting the underlying IndexedDB database. As such, it always can be used as a fail-safe to get a clean slate, as shown below.

            @@ -961,27 +961,27 @@

    • 3.6. Iteration

    -

    The KVStorageArea interface supports asynchronous iteration.

    +

    The KVStorageArea interface supports asynchronous iteration.

    for await (const key of storage.keys()) { ... }

    Retrieves an async iterator containing the keys of all entries in this storage area.

    -

    Keys will be yielded in ascending order; roughly, segregated by type, and then sorted within each type. They will be key round-tripped from their original form.

    +

    Keys will be yielded in ascending order; roughly, segregated by type, and then sorted within each type. They will be key round-tripped from their original form.

    for await (const value of storage.values()) { ... }

    Retrieves an async iterator containing the values of all entries in this storage area.

    -

    Values will be yielded in the same order as for keys(). They will be structured-deserialized from their original form.

    +

    Values will be yielded in the same order as for keys(). They will be structured-deserialized from their original form.

    for await (const [key, value] of storage.entries()) { ... }
    for await (const [key, value] of storage) { ... }

    Retrieves an async iterator containing two-element [key, value] arrays, each of which corresponds to an entry in this storage area.

    -

    Entries will be yielded in the same order as for keys(). Each key and value will be key round-tripped and structured-deserialized from its original form, respectively.

    +

    Entries will be yielded in the same order as for keys(). Each key and value will be key round-tripped and structured-deserialized from its original form, respectively.

    All of these iterators provide live views onto the storage area: modifications made to entries sorted after the last-returned one will be reflected in the iteration.

    - The asynchronous iterator initialization steps for KVStorageArea, given storageArea and asyncIterator, are: + The asynchronous iterator initialization steps for KVStorageArea, given storageArea and asyncIterator, are:

    1. Set asyncIterator’s last key to not yet started.

      @@ -999,7 +999,7 @@

      Let keyRequest be the result of performing the steps listed in the description of IDBObjectStore's getKey() method on store, given the argument range.

    2. Let valueRequest be the result of performing the steps listed in the description of IDBObjectStore's get() method on store, given the argument range.

      -

      Note: The iterator returned from keys() discards the value. Implementations could avoid constructing valueRequest in that case.

      +

      Note: The iterator returned from keys() discards the value. Implementations could avoid constructing valueRequest in that case.

    3. Let promise be a new promise in the relevant Realm of asyncIterator.

    4. @@ -1051,10 +1051,10 @@

      .log(keysSeen); // logs 10, 20, 25, 30 -

      That is, calling keys() does not create a snapshot as of the time it was called; it returns a live asynchronous iterator, that lazily retrieves the next key after the last-seen one.

      +

      That is, calling keys() does not create a snapshot as of the time it was called; it returns a live asynchronous iterator, that lazily retrieves the next key after the last-seen one.

    - Assuming you knew that that you only stored JSON-compatible types in the KVStorageArea storage, you could use the following code to send all locally-stored entries to a server: + Assuming you knew that that you only stored JSON-compatible types in the KVStorageArea storage, you could use the following code to send all locally-stored entries to a server: 
    const entries = [];
 for await (const entry of kvStorage.entries()) {
   entries.push(entry);
@@ -1069,9 +1069,9 @@ 
    });
    -

    3.7. backingStore

    +

    3.7. backingStore

    -
    { database, store, version } = storage.backingStore +
    { database, store, version } = storage.backingStore

    Returns an object containing all of the information necessary to manually interface with the IndexedDB backing store that underlies this storage area:

      @@ -1082,7 +1082,7 @@

      version will be the number 1.

    -

    It is good practice to use the backingStore property to retrieve this information, instead of memorizing the above factoids.

    +

    It is good practice to use the backingStore property to retrieve this information, instead of memorizing the above factoids.

      @@ -1107,7 +1107,7 @@

    - Consider a checklist application, which tracks the Pokémon a user has collected. It might use a KVStorageArea storage like so: + Consider a checklist application, which tracks the Pokémon a user has collected. It might use a KVStorageArea storage like so: 
    bulbasaur.onchange = () => kvStorage.set("bulbasaur", bulbasaur.checked);
 ivysaur.onchange = () => kvStorage.set("ivysaur", ivysaur.checked);
 venusaur.onchange = () => kvStorage.set("venusaur", venusaur.checked);
@@ -1121,7 +1121,7 @@ 
    };

    However, our developer starts getting bug reports from their users: if the users happen to open up the checklist app in a second tab while they’re evolving in the first tab, the second tab will sometimes see that their Bulbasaur has disappeared, without ever turning into an Ivysaur! A Pokémon has gone missing!

    -

    The solution here is to step beyond the comfort zone of KV storage, and start using the full power of IndexedDB: in particular, its transactions feature. The backingStore getter is the gateway to this world:

    +

    The solution here is to step beyond the comfort zone of KV storage, and start using the full power of IndexedDB: in particular, its transactions feature. The backingStore getter is the gateway to this world:

    const { database, store, version } = kvStorage.backingStore;
 const request = indexedDB.open(database, version);
 request.onsuccess = () => {
@@ -1162,7 +1162,7 @@ 
    4
    - To perform a database operation given a KVStorageArea area, a mode string mode, and a set of steps steps that operate on an IDBTransaction transaction and an IDBObjectStore store: + To perform a database operation given a KVStorageArea area, a mode string mode, and a set of steps steps that operate on an IDBTransaction transaction and an IDBObjectStore store:

    1. Assert: area.[[DatabaseName]] is a string (and in particular is not null).

      @@ -1181,7 +1181,7 @@

      4

    - To initialize the database promise for a KVStorageArea area: + To initialize the database promise for a KVStorageArea area:

    1. Set area.[[DatabasePromise]] to a new promise in the relevant Realm of area.

      @@ -1197,13 +1197,13 @@

      4

    2. Let database be request’s result.

    3. -

      Check the database schema for database. If the result is false, reject area.[[DatabasePromise]] with an "InvalidStateError" DOMException and abort these steps.

      +

      Check the database schema for database. If the result is false, reject area.[[DatabasePromise]] with an "InvalidStateError" DOMException and abort these steps.

    4. Add a simple event listener to database for "close" that sets area.[[DatabasePromise]] to null.

      This means that if the database is closed abnormally, future invocations of perform a database operation will attempt to reopen it.

    5. Add a simple event listener to database for "versionchange" that performs the steps listed in the description of IDBDatabase's close() method on database, and then sets area.[[DatabasePromise]] to null.

      -

      This allows attempts to upgrade the underlying database, or to delete it (e.g. via the clear() method), to succeed. Without this, if two KVStorageArea instances were both open referencing the same underlying database, clear() would hang, as it only closes the connection maintained by the KVStorageArea it is invoked on.

      +

      This allows attempts to upgrade the underlying database, or to delete it (e.g. via the clear() method), to succeed. Without this, if two KVStorageArea instances were both open referencing the same underlying database, clear() would hang, as it only closes the connection maintained by the KVStorageArea it is invoked on.

    6. Resolve promise with database.

    @@ -1264,9 +1264,9 @@

    4

    Most notably, using the allowed as a key predicate ensures that IDBKeyRange objects, or any other special object that is accepted as a query in future IndexedDB specification revisions, will be disallowed. Only straightforward key values are accepted by the KV storage API.

    • -

    Key round-tripping refers to the way in which JavaScript values are processed by first being passed through IndexedDB’s convert a value to a key operation, then converted back through its convert a key to a value operation. Keys returned by the keys() or entries() methods will have gone through this process.

    -

    Notably, any typed arrays or DataViews will have been "unwrapped", and returned back as just ArrayBuffers containing the same bytes. Also, similar to the structured-serialization/deserialization process, any "expando" properties or other modifications will not be preserved by key round-tripping.

    -

    For primitive string or number values, there’s no need to worry about key round-tripping; the values are indistinguishable.

    +

    Key round-tripping refers to the way in which JavaScript values are processed by first being passed through IndexedDB’s convert a value to a key operation, then converted back through its convert a key to a value operation. Keys returned by the keys() or entries() methods will have gone through this process.

    +

    Notably, any typed arrays or DataViews will have been "unwrapped", and returned back as just ArrayBuffers containing the same bytes. Also, similar to the structured-serialization/deserialization process, any "expando" properties or other modifications will not be preserved by key round-tripping.

    +

    For primitive string or number values, there’s no need to worry about key round-tripping; the values are indistinguishable.

    To get the range for a key key:
      @@ -1363,7 +1363,7 @@

      https://tc39.github.io/ecma262/#sec-date-objectsReferenced in:

  • Sort list in ascending order by using postscriptName as the sort key and store the result as list.

    @@ -1017,20 +1017,20 @@

    Make "selected by the user" more spec-like.

    • -

    6.2. The FontMetadata interface

    -

    A FontMetadata provides details about a font face. Each FontMetadata has an associated font representation.

    +

    6.2. The FontMetadata interface

    +

    A FontMetadata provides details about a font face. Each FontMetadata has an associated font representation.

    -
    metadata . postscriptName +
    metadata . postscriptName

    The PostScript name for the font. Example: "Arial-Bold". The OpenType spec expects this to be encoded in a subset of ASCII and is unique for metadata

    -
    metadata . fullName +
    metadata . fullName

    The full font name, including family subfamily names. Example: "Arial Bold"

    -
    metadata . family +
    metadata . family

    The font family name. Example: "Arial"

    -
    metadata . style +
    metadata . style

    The font style (or subfamily) name. Example: "Regular", "Bold Italic"

    @@ -1039,10 +1039,10 @@

    interface FontMetadata { Promise<Blob> blob(); - readonly attribute USVString postscriptName; - readonly attribute USVString fullName; - readonly attribute USVString family; - readonly attribute USVString style; + readonly attribute USVString postscriptName; + readonly attribute USVString fullName; + readonly attribute USVString family; + readonly attribute USVString style; };
    @@ -1063,9 +1063,9 @@

    Include name ID 3 (Unique identifier) as well?

    -
    await blob = metadata . blob() +
    await blob = metadata . blob()
    -

    Request the font data of metadata. The result blob contains data bytes.

    +

    Request the font data of metadata. The result blob contains data bytes.

    @@ -1077,7 +1077,7 @@

    Run these steps in parallel:

    1. -

      Let blob be a new Blob whose contents are this's data bytes and type attribute is `application/octet-stream`.

      +

      Let blob be a new Blob whose contents are this's data bytes and type attribute is `application/octet-stream`.

    2. Resolve promise with blob.

    @@ -1089,10 +1089,10 @@

    7. Document internationalization consideration, e.g. string localization

    7.1. Font Names

    The `name` table in OpenType [OPENTYPE] fonts allows names (family, subfamily, etc) to have multilingual strings, using either platform-specific numeric language identifiers or language-tag strings conforming to [BCP47]. For example, a font could have family name strings defined for both `en` and `zh-Hant-HK`.

    -

    The FontMetadata properties postscriptName, fullName, family, and style are provided by this API simply as strings, using the `en` locale. This matches the behavior of the FontFace family property.

    +

    The FontMetadata properties postscriptName, fullName, family, and style are provided by this API simply as strings, using the `en` locale. This matches the behavior of the FontFace family property.

    The above does not match the spec/implementation. Resolve the ambiguity.

    Web applications that need to provide names in other languages can request and parse the `name` table directly.

    -

    Should we define an option to the query() method to specify the desired language for strings (e.g. {lang: 'zh'}), falling back to `en` if not present?

    +

    Should we define an option to the query() method to specify the desired language for strings (e.g. {lang: 'zh'}), falling back to `en` if not present?

    8. Accessibility considerations

    There are no known accessibility impacts of this feature.

    9. Security considerations

    @@ -1620,7 +1620,7 @@

    #font-representation-data-bytesReferenced in: