From c4b948bd8130b886b05904770d6f13b94c8da4bd Mon Sep 17 00:00:00 2001 From: Matt Raible Date: Wed, 8 Apr 2026 11:12:36 -0600 Subject: [PATCH] Fix iframe selector for Charlotte AI compatibility Use iframe[name="portal"] instead of bare iframe selector to avoid strict mode violation when Charlotte AI adds a second iframe to the page. --- e2e/src/pages/HelloExtensionPage.ts | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/e2e/src/pages/HelloExtensionPage.ts b/e2e/src/pages/HelloExtensionPage.ts index 055977b..cc4b831 100644 --- a/e2e/src/pages/HelloExtensionPage.ts +++ b/e2e/src/pages/HelloExtensionPage.ts @@ -58,11 +58,11 @@ export class HelloExtensionPage extends SocketNavigationPage { } // Verify iframe loads - await expect(this.page.locator('iframe')).toBeVisible({ timeout: 15000 }); + await expect(this.page.locator('iframe[name="portal"]')).toBeVisible({ timeout: 15000 }); this.logger.info('Extension iframe loaded'); // Verify iframe content - const iframe: FrameLocator = this.page.frameLocator('iframe'); + const iframe: FrameLocator = this.page.frameLocator('iframe[name="portal"]'); // Check for "Foundry Functions Demo" text await expect(iframe.getByText(/Foundry Functions Demo/i)).toBeVisible({ timeout: 10000 });