Update web-platform-tests to revision b'a85f0dfe538b9cb894388a65dba7a2a21db050c7' (#30879)

tests/wpt/meta/webmessaging/message-channels/close-event/close-event.tentative.any.js.ini

@@ -1,10 +0,0 @@
-[close-event.tentative.any.html]
-  expected: TIMEOUT
-  [Close event listener added with onclose must be called.]
-    expected: TIMEOUT
-
-
-[close-event.tentative.any.worker.html]
-  expected: TIMEOUT
-  [Close event listener added with onclose must be called.]
-    expected: TIMEOUT

tests/wpt/meta/webmessaging/message-channels/close-event/document-destroyed.tentative.window.js.ini

@@ -0,0 +1,10 @@
+[document-destroyed.tentative.window.html]
+  expected: ERROR
+  [The context is navigated to a new document and a close event is fired.]
+    expected: TIMEOUT
+
+  [The window is closed and a close event is fired.]
+    expected: NOTRUN
+
+  [The iframe is deleted and a close event is fired.]
+    expected: NOTRUN

tests/wpt/meta/webmessaging/message-channels/close-event/entangled-after-back-forward-cache-restore.https.tentative.window.js.ini

@@ -0,0 +1,3 @@
+[entangled-after-back-forward-cache-restore.https.tentative.window.html]
+  [MessagePort still works after the page is restored from BFCache]
+    expected: FAIL

tests/wpt/meta/webmessaging/message-channels/close-event/explicitly-closed.tentative.window.js.ini

@@ -0,0 +1,7 @@
+[explicitly-closed.tentative.window.html]
+  expected: TIMEOUT
+  [Close event on port2 is fired when port1 is explicitly closed]
+    expected: TIMEOUT
+
+  [Close event on port2 is fired when port1, which is in a different window, is explicitly closed.]
+    expected: TIMEOUT

tests/wpt/meta/webmessaging/message-channels/close-event/garbage-collected.tentative.any.js.ini

@@ -0,0 +1,8 @@
+[garbage-collected.tentative.any.html]
+  [Entangled port is garbage collected, and the close event is fired.]
+    expected: FAIL
+
+
+[garbage-collected.tentative.any.worker.html]
+  [Entangled port is garbage collected, and the close event is fired.]
+    expected: FAIL