From ec53481c3f5b25f6353eacb80f871423232a6b2b Mon Sep 17 00:00:00 2001 From: Andrew Williams Date: Mon, 9 Dec 2024 16:45:21 +0900 Subject: [PATCH] Replace existing usage of blob URL entry's object As suggested in https://github.com/whatwg/fetch/pull/1783#issuecomment-2493209801, this change updates an existing use of blob URL entry's object so that the "obtain a blob object" algorithm is used instead. This algorithm was added in https://github.com/w3c/FileAPI/pull/201. --- source | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/source b/source index 93421b8c267..893a2799c62 100644 --- a/source +++ b/source @@ -3481,8 +3481,8 @@ a.setAttribute('href', 'https://example.com/'); // change the content attribute
  • The concept of read errors
  • Blob URL Store
  • blob URL entry and its - object and environment
    • +
  • The obtain a blob object algorithm
    • @@ -36782,11 +36782,24 @@ interface MediaError { object is as follows:

      -

    1. If the algorithm was invoked with media provider object or a URL - record whose blob URL entry is a blob - URL entry whose object is a media - provider object, then let mode be local. Otherwise, let mode - be remote.

      2. +

    2. Let mode be remote.

      3. + +
    3. +

      If the algorithm was invoked with media provider object, then set + mode to local.

      + +

      Otherwise:

      + +
        +

      1. Let object be the result of obtaining + a blob object using the URL record's blob URL entry and the media element's + node document's relevant settings object.

        2. + +

      2. If object is a media provider object, then set mode + to local.

        3. +
      +

    4. If mode is remote, then let the current media resource be the resource given by the URL record passed to this algorithm; otherwise, let the