From a756b851bf0c7e1455c84e4a85d20bd6357e7ff7 Mon Sep 17 00:00:00 2001 From: Ms2ger Date: Wed, 25 Feb 2026 11:14:19 +0100 Subject: [PATCH] lib: improve argument handling in Blob constructor As specified in WebIDL (), the fields of a dictionary need to be read in lexicographical order. --- lib/internal/blob.js | 2 +- test/wpt/status/FileAPI/blob.json | 1 - 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/lib/internal/blob.js b/lib/internal/blob.js index 46abb4f793c465..e42773a8d03dcc 100644 --- a/lib/internal/blob.js +++ b/lib/internal/blob.js @@ -149,8 +149,8 @@ class Blob { } validateDictionary(options, 'options'); let { - type = '', endings = 'transparent', + type = '', } = options ?? kEmptyObject; endings = `${endings}`; diff --git a/test/wpt/status/FileAPI/blob.json b/test/wpt/status/FileAPI/blob.json index 3bbd15087a02ac..a82a9cb0cfdb11 100644 --- a/test/wpt/status/FileAPI/blob.json +++ b/test/wpt/status/FileAPI/blob.json @@ -10,7 +10,6 @@ "blobParts not an object: BigInt with BigInt.prototype[Symbol.iterator]", "blobParts not an object: Symbol with Symbol.prototype[Symbol.iterator]", "Getters and value conversions should happen in order until an exception is thrown.", - "options properties should be accessed in lexicographic order.", "Arguments should be evaluated from left to right." ], "flaky": [