Update web-platform-tests to revision 0d4300c5045a5587c2eb3d1416b11ffeecf5dadc

1 files changed, 3 insertions, 3 deletions

diff --git a/tests/wpt/web-platform-tests/css/css-layout-api/fallback-layout-invalid-child.https.html b/tests/wpt/web-platform-tests/css/css-layout-api/fallback-layout-invalid-child.https.html
index 19b4188a839..567c3f7f745 100644
--- a/tests/wpt/web-platform-tests/css/css-layout-api/fallback-layout-invalid-child.https.html
+++ b/tests/wpt/web-platform-tests/css/css-layout-api/fallback-layout-invalid-child.https.html
@@ -32,15 +32,15 @@
 registerLayout('bad-child-layout', class {
   static get inputProperties() { return ['--fail']; }
 
-  *intrinsicSizes() {}
-  *layout(children, _, __, styleMap) {
+  async intrinsicSizes() {}
+  async layout(children, _, __, styleMap) {
     if (styleMap.get('--fail').toString() !== 'true') {
       this.child = children[0];
     }
 
     // Try to perform layout on the child. If its invalid (we skipped the if
     // statement above) we should fallback to block layout.
-    const fragment = yield this.child.layoutNextFragment({});
+    const fragment = await this.child.layoutNextFragment({});
 
     return {autoBlockSize: 0, childFragments: [fragment]};
   }