From 3a9c684f5ea588d324eb32d5f8bdbc4c2961b142 Mon Sep 17 00:00:00 2001 From: Lilleman auf Larv Date: Sun, 8 Nov 2026 23:17:32 +0100 Subject: [PATCH] Expect WebKit's plain-http cross-origin-isolation warning in the console guard --- e2e-tests/console-guard.ts | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/e2e-tests/console-guard.ts b/e2e-tests/console-guard.ts index ef9389f..5910d77 100644 --- a/e2e-tests/console-guard.ts +++ b/e2e-tests/console-guard.ts @@ -12,10 +12,14 @@ import { expect, test as base, type BrowserContext, type Page } from "@playwrigh const problems: string[] = []; const allowed: RegExp[] = []; -// The one message the stack itself provokes: the runner reaches `web`/`proxy` by container name over +// The messages the stack itself provokes: the runner reaches `web`/`proxy` by container name over // plain http, and only a `localhost` origin is trustworthy without TLS — so Chromium drops the COOP -// header the app sends and says so on every page. Over https, where a deployment serves, it applies. -const EXPECTED = [/^console\.error: The Cross-Origin-Opener-Policy header has been ignored/]; +// header the app sends, and WebKit reports the page not cross-origin isolated, on every page. Over +// https, where a deployment serves, the header applies. +const EXPECTED = [ + /^console\.error: The Cross-Origin-Opener-Policy header has been ignored/, + /^console\.warning: This document is not cross-origin isolated because the document is not a secure context/, +]; // Allow a message for the current test only, when the page under test provokes it on purpose. export function allowConsole(...patterns: RegExp[]): void {