Bug 1945286 [wpt PR 50422] - Remove special boolean handling in ResolveToConfigResolved::React(), a=testonly

Automatic update from web-platform-tests
Remove special boolean handling in ResolveToConfigResolved::React()

Instead of following standard JS rules for coercing an aribtary value to
a boolean, it was treating non-booleans as false. A use counter shows
that this behavior isn't relied upon, so use the standard behavior.

Change-Id: I3b4424064f6728b8206166d3df86dd42b71af520
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6219805
Commit-Queue: Nate Chapin <[email protected]>
Reviewed-by: Maks Orlovich <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1414449}

--

wpt-commits: 74bb7c02d56981377136ea189b01b94d8dbbdb52
wpt-pr: 50422

Author: natechapin

testing/web-platform/tests/fenced-frame/resolve-to-config-promise.https.html

@@ -64,16 +64,15 @@
 promise_test(async(t) => {
   const key = token();
 
-  // This should still resolve, but resolve to a URN.
   const urn = await generateURNFromFledge("resources/embeddee.html", [key],
-      [], delayValue("invalid", 0));
-  assert_false(urn instanceof FencedFrameConfig);
+      [], delayValue("non-boolean", 0));
+  assert_true(urn instanceof FencedFrameConfig);
   const fencedframe = attachFencedFrame(urn);
 
   const page1_resp = await nextValueFromServer(key);
   assert_equals(page1_resp, "PASS",
       "The page should have loaded.");
-}, 'resolveToConfig set to a promise that resolves to an invalid value');
+}, 'resolveToConfig set to a promise that resolves to an non-boolean value');
 
 </script>
 </body>